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

[Joel Saunders]

I have 3 and don't ever use them anyway  (Remember that I inherited this system so I didn't want to make massive changes as it was a "side" task).
The 3 are /Login /WAYF, and /DS

I will drop them and modify the SSO section to use my default IDPs entity id

Thanks all...

JOel

-----Original Message-----
From: users <users-bounces at shibboleth.net> On Behalf Of Cantor, Scott
Sent: Tuesday, March 12, 2019 11:24 AM
To: Shib Users <users at shibboleth.net>
Subject: Re: 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

On 3/12/19, 11:18 AM, "users on behalf of Joel Saunders" <users-bounces at shibboleth.net on behalf of Joel.Saunders at zones.com> wrote:

> I'm wondering if this is a check in the new version.

The warning is, the behavior isn't.

> 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?

A discoveryURL is never used if you're pointing it at an IdP to use, it never gets a chance to see it. And you do not have what would be needed in there to just pull the SSO element, that takes much more XML than you have there, all the AssertionConsumerService handlers and so forth. So you have no real choice, you need to get rid of the SessionInitiators.

-- Scott


--
For Consortium Member technical support, see https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.shibboleth.net_confluence_x_coFAAg&d=DwICAg&c=bFSfV3JDZVFjkVdrOg1Bnsgwku-x_EGNRi2KNxwvClI&r=WG-pl0WpwyPk-r6oNnUhsoAUBdVNpC8ryokTG8RkffA&m=LdDWdRoBG5v-wVyO3MPUcMKwMIwF3DNrBiAuvN5epDY&s=Pmb_nrVQ2xIsYLRDlBm_bcEQr9ZzK4pcnVuolVPC0II&e=
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net