Define a relying party profile for AuthnRequestsSigned="true"
Karla Borecky
kborecky at smith.edu
Thu Feb 25 11:36:24 EST 2016
I don't think this exact question has been asked, but if so, please forgive
me.
I am working with a colleague to configure Banner 8 ssomanager. Their
metadata specifies
AuthnRequestsSigned="true"
I see that the default for all SAML profiles is
signedRequestsPredicate = alwaysFalse
I don't know if this is the setting that corresponds to the SP's
"AuthnRequests" one - so that's my first question.
If this is the correct predicate, can I set it to be true for them?
This is what I have now, containing settings they have either documented as
being necessary, or as listed in their metadata. The boldfaced bit would be
my best guess at what this new setting would be:
<bean parent="RelyingPartyByName" c:relyingPartyIds="ssomanager">
<property name="profileConfigurations">
<list>
<bean parent="SAML2.SSO"
p:encryptAssertions="false"
p:encryptNameIDs="false"
p:signAssertions="true"
* p:signedRequests="true"* />
</list>
</property>
</bean>
If this isn't possible, I can ask my colleague to see if there is a setting
for this she can turn off. But I thought I'd ask.
Thank you so much -
Karla B
PS I did read the posts about the complications of always requiring signed
Authn requests, but I just want to do it for this one SP. (Or if there are
others at some point, I would add them here.)
--
Karla Borecky
Systems Administrator
ITS
Smith College
Northampton, MA 01063
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20160225/c95a5a66/attachment.html>
More information about the users
mailing list