Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. A user visits the URL of a service (like a wiki) and clicks a link to authenticate via SCZ
  2. The (browser of the) user is (automatically) redirected to the SCZ component SaToSa
  3. If necessary, a Where-Are-You-From-screen is presented so the user can select the IdP where he/she wants to authenticate
  4. After the optional WAYF, the user is directed back to SaToSa (almost invisible to the user)
  5. The user is directed to his/her IdP/institution (can be via SURFconext, which would be transparent for the user, can be eduGAIN or an IdP connected to SaToSa directly)
  6. After successful authentication at the IdP, the user is redirected back to SaToSa, with her attributes. If authentication is via SURFconext, SURFconext is using an Attribute Release Policy (ARP) to only release R&S-attributes to SaToSa
  7. SaToSa uses the EPPN-attribute a combination of attributes that uniquely identify the user and SP entityID to gather supplementary CO specific COManage attributes and injects them into the SAML flow, while removing the original IdP attributes. If the EPPN-attribute is identifying attributes are not supplied, SaToSa redirects the user directly to the service via consent page, supplying the service only with attributes it received from the IdP. It is up to the receiving service to operate (authorize) on the supplied attributeswill send an empty assertion.
  8. If the IdP has provided an EPPNidentifying attributes, SaToSa searches a database the SCZ component COmanage has provisioned and uses EPPN and entity id them together with the entityID of the service to find the CO and CO-specific attributes. Only attributes necessary for the visited service will be injected in the available assertion and returned by SaToSa.
  9. SaToSa can be configured to show a Consent formInform screen. If so configured, a consent form is shownWhether or not and for what attributes the user consents is returned to SaToSaan inform is shown, telling the user she is leaving the boundaries of the institution explaining the (legal) consequences of this action.
  10. The user can only choose to completely grant or deny continuation to the service. There is no middle road on a per-attribute basis. If the user chooses to deny access, the flow stops here.
  11. If consent was given (or configured not to be required) SaToSa combines the attributes received from the IdP and from COmanage and supplies the will send the SP/CO specific attributes to the service.
  12. Based on the internals of the service (like required attributes and whether they are supplied), the user does or does not get access to the service.

...