SHA1 signed authn request issue

Brent Putman putmanb at georgetown.edu
Fri Mar 10 16:54:06 EST 2017



On 3/10/17 3:29 PM, Yavor Yanakiev wrote:
>
> Since we were able to modify the metadata we
> set AuthnRequestsSigned="false"
>
> <md:SPSSODescriptor WantAssertionsSigned="false"
> AuthnRequestsSigned="false"
> protocolSupportEnumeration="urn:oasis:names:tc:SAML:2.0:protocol">
> <md:KeyDescriptor use="signing">
>
> but it didn't do the trick. 
>

Not relevant to your issue, but: for the record that metadata attribute
doesn't do what you think it does.  It only makes sense to set
AuthnRequestsSigned="true", which then tells the IdP that AuthnRequests
from the SP must be signed, or they will be rejected outright. It's a
statement of policy, basically.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20170310/f2b9a457/attachment-0001.html>


More information about the users mailing list