SLIDE 4 4
What just happened?
- 1. Access SP (x)
- 2. Choose IdP (1)
- 3. Login
- 4. Consent
- 5. Access
- 5. Access
- WARNING: Technical explanation follows!
–
Sh m
Architecture SAML/Shibboleth v2.x
DS r der
HTTP redirect HTTP interaction
Webserver
hibboleth
x
User Agent/Browser
Identity Provid
Service Provider
Shibboleth service
14
Identity Provider
Webserver
SAML2.0 profile: Web browser SSO + HTTP POST binding Initial request from UA to document X No active Shibboleth session, UA redirected to DS
Sh m
Architecture SAML/Shibboleth v2.x
DS r der
HTTP redirect HTTP interaction
SP takes back t l
Webserver
hibboleth
x
User Agent/Browser
Identity Provid
control
Service Provider
Shibboleth service
15
Identity Provider
Webserver
DS asks UA to choose an IdP (if not already set in cookie) Redirect UA back to SP with selected IdP as parameter.
Sh m
Architecture SAML/Shibboleth v2.x
DS r der
HTTP redirect HTTP interaction
Webserver
hibboleth
x
User Agent/Browser
Identity Provid
Service Provider
Shibboleth service
16
Identity Provider
Webserver
SP sends SAML Authentication request to the IdP. IdP prompts the UA for credentials, if necessary. IdP uses backend to verify credentials (LDAP, ADDS, SQL, etc)