IdP does not release attributes

Rod Widdowson rdw at steadingsoftware.com
Sat Jul 29 11:22:32 EDT 2017


>  <ApplicationDefaults entityID="https://sso-med1.imib.rwth-aachen.de/shibboleth"
>         <SSO entityID="https://sso-med1.imib.rwth-aachen.de/shibboleth">
> <md:EntityDescriptor xmlns:md="urn:oasis:names:tc:SAML:2.0:metadata" (..) entityID="https://sso-med1.imib.rwth-aachen.de">
> shouldn't these IDs match?

Yes, which probably means that the SP isn’t reading what you think it is.  What does the "Shibboleth.sso/Status" endpoint say?

But note that in your log you have apparently logged in as "https://sso-med1.imib.rwth-aachen.de" (last line).

I think you probably want to chase that down.  There may well be more going on but something is in two minds as to what is going on,
and until such time as you know the SP is reading the configuration you think it is you are wasting you time.

If you need to debug the IdP, you will need to turn up category "net.shibboleth.idp.attribute" as per [1]

[1] https://wiki.shibboleth.net/confluence/display/IDP30/LoggingConfiguration#LoggingConfiguration-LoggingCategories




More information about the users mailing list