Shibboleth won't sign assertions?

[Benjamin Cherian]

Try p:signAssertions=“true”. That worked for me on IdP 3.0

From: Jeremy Morton <jez9999 at gmail.com<mailto:jez9999 at gmail.com>>
Reply-To: Shib Users <users at shibboleth.net<mailto:users at shibboleth.net>>
Date: Wednesday, February 4, 2015 at 11:18 AM
To: Shib Users <users at shibboleth.net<mailto:users at shibboleth.net>>
Subject: Shibboleth won't sign assertions?

I'm trying to override Shibboleth's default assertion signing behaviour.  I don't want assertions encrypted for my SP, but I do want them signed.  I have this config in relying-party.xml:

    <util:list id="shibboleth.RelyingPartyOverrides">
        <bean parent="RelyingPartyByName" c:relyingPartyIds="http://localhost:65231/">
            <property name="profileConfigurations">
                <list>
                    <bean parent="SAML2.SSO" p:encryptAssertions="false" p:signAssertions="always" />
                </list>
            </property>
        </bean>
    </util:list>

... where http://localhost:65231/ is identical to my EntityDescriptor entityID in metadata-providers.xml.  It seems to match, because assertions returned to that SP are no longer encrypted, by they are not signed either.  Only the overall response is signed.  Any ideas why the assertions are not signed?

Best regards,
Jeremy Morton (Jez)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://shibboleth.net/pipermail/users/attachments/20150204/2c232b84/attachment.html