Unknown or Unusable Identity Provider for Shib 3.2 SP

Peter Schober peter.schober at univie.ac.at
Tue Jun 4 18:12:05 UTC 2024


Steve Platz via users <users at shibboleth.net> [2024-06-04 19:15 CEST]:
> You'll have to forgive me since I am not the person who has
> configured the SP software, nor do I have direct access to it, I'm
> trying to provide support to the person currently managing it.

If the only change was the one on the IDP-side you mentioned then you
might get away without any access nor knowledge about the SP.

Note that SP version 3.2 is not current and no longer supported by the
Shibboleth project, https://shibboleth.atlassian.net/wiki/spaces/SP3/

> I do manage the IdP, which was recently upgraded to simpleSAMLphp
> 2.x. The metadata that the IdP provides now sets an explicit
> entityID, where before this value was __DYNAMIC__ and automatically
> generated depending on the environment. Updating the entityID to use
> an explicit, permanent value seems to have resulted in the Shib SP
> errors, but again I don't have access myself to the logs on that
> provider.

Well, the first thing to do on the IDP side then is to explicitly set
the entityID to the exact same value that was autogenerated before.
(You can probably still see this in the metadata about the IDP you
gave to other SPs.)
I would expect that to take care of the "unknown IDP" error.

-peter


More information about the users mailing list