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) directed redirected to the SCZ component SaToSaSATOSA
  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 SaToSato 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 to SATOSA directly)
  6. After successful authentication at the IdP, the user is redirected back to SaToSaSATOSA, with her their attributes. If authentication is via SURFconext, SURFconext is using an Attribute Release Policy (ARP) to only release R&S-attributes to SaToSaSaToSa checks for the EPPN-attribute. If this attribute is not supplied, SaToSa redirects the user to the service via consent page, supplying the service with consented attributes it received from the IdP. And the flow ‘stops’ at this point. Whether the service is able to operate with the supplied attributes is not something SCZ can decide. to SATOSA
  7. SATOSA uses a combination of attributes that uniquely identify the user and SP entityID to gather supplementary CO specific COmanage attributes.
  8. If the IdP has provided an EPPNidentifying attributes, SaToSa  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 form. If so configured, a consent form is shown
  10. Whether or not and for what attributes the user consents is returned to SaToSa:
    1. On initial provisioning of the user in COmanage, so where COmanage is the SP, the IdP attributes can be used (for instance when we want to use the name supplied by the user's IdP). 
    2. In all other cases, the CO specific COmanage attributes are injected into the SAML flow to the SP, while removing the original IdP attributes. If the identifying attributes are not supplied, SATOSA will send an empty assertion.
  11. SATOSA can be configured to show an Inform screen. If so configured, an inform is shown, telling the user she is leaving the boundaries of the institution explaining the (legal) consequences of this action.
  12. 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.
  13. If consent was given (or configured not to be required) SaToSa combines the attributes received from the IdP and from COmanage and supplies the  SATOSA will send the SP/CO specific attributes to the service.
  14. 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.

More info about the technical components and their relations that make up the SCZ environment can be found on Technical overview of SCZ . How to configure invite-flows, invite users etc can be found in (subpages of) End user documentation SCZ COmanage .