SessionInitiator handler at duplicate Location (/Login) will not be processed for application (default) - default IDP function not working since SP upgrade from v2 to v3
Nate Klingenstein
ndk at signet.id
Tue Mar 12 11:21:09 EDT 2019
Joel,
> <!-- Default example directs to a specific IdP's SSO service (favoring SAML 2 over Shib 1). -->
> <!-- change entityID to your identity provider entity ID -->
> <SessionInitiator type="Chaining" Location="/Login" isDefault="true" id="Intranet"
> relayState="cookie" entityID="https://idphostname/idp/shibboleth">
> <SessionInitiator type="SAML2" defaultACSIndex="1" acsByIndex="false" template="bindingTem
> plate.html"/>
> <SessionInitiator type="Shib1" defaultACSIndex="5"/>
> </SessionInitiator>
>
> ----------------------------------------------------------------------------------------------------------
> Should I remove the SessionInitiator section and change the SSO section to use the entitiyID option with my IDP vs. the discoveryURL since I still need the one IDP to default to?
Yes. If you need a second SessionInitiator that behaves differently, then you'll need to remove the SSO element and add another SessionInitiator, but it would make far more sense to just set an entityID attribute on your SSO element.
Take care,
Nate.
More information about the users
mailing list