Allowing the Metadata to determine end-points
Cantor, Scott
cantor.2 at osu.edu
Wed Jan 27 10:25:16 EST 2016
On 1/27/16, 10:17 AM, "users on behalf of Antony den Dulk" <users-bounces at shibboleth.net on behalf of antony at selestiasolutions.com> wrote:
>
>
>The third option is what I was asked to use by the admin of the IdP (at least from what I understood from him).
Shibboleth SPs don't ever send nothing. At least, I don't think it will, I've been mostly on the IdP now for years, so details get hard to recall. I can't think of any scenario in which it would do that.
> "By Value" is the actual URI to use and "By Index" is using an identifier that lets the IdP know which URI to use from the Metadata? Correct me if my understanding is incorrect.
Yes, "index" is referring to the corresponding index XML attribute in the AssertionConsumerService element in metadata.
>So Shibboleth does not support option 3, which means I need to use one of the other two. "By Value" I take it is the standard, if I want to switch it to "By Index" (even though it is horrible) what do I need to do (link to documentation would be great)?
I can't imagine how that could help, but you set acsByIndex to true in the <SSO> element.
https://wiki.shibboleth.net/confluence/display/SHIB2/NativeSPSessionInitiator
SessionInitiator options/settings can be set in the <SSO> element and are "picked up" by the auto-generated SessionInitiator plugins it instantiates when that shorter syntax is used.
-- Scott
More information about the users
mailing list