shibboleth - stopped working after package update
Peter Schober
peter.schober at univie.ac.at
Wed Jul 3 07:34:48 EDT 2013
* Pedro Albuquerque <pedroalb at ebi.ac.uk> [2013-07-03 13:24]:
> <Location /Shibboleth.sso>
> Satisfy Any
> Allow from all
> </Location>
>
> I just simply removed it and worked.
> My question is: Why the use of Satisfy Any when the login handler is
> on /Shibboleth.sso/Login? My drupal site points its login handler to
> that location. If that Satisfy Any directive is there, it cannot
> authenticate.
This location directive will also match anything "below"
/Shibbboleth.sso, so it will also match /Shibboleth.sso/Login.
Obviously you cannot protect endpoints at which Shibboleth initiates
sessions or recieves SAML assertions with the Shibboleth software, you
d never be able to log in (you can't mandate a valid session to allow
initiating of sessions).
So whatever is broken, access to /Shibboleth.sso needs to be
unrestricted from any access control and also cannot be routed to any
other application (e.g. Drupal),
-peter
More information about the users
mailing list