This page shows the steps a user goes through when accessing a service connected to the SCZ-environment (after initial sign-up with a CO in COmanage):
- A user visits the URL of a service (like a wiki) and clicks a link to authenticate via SCZ
- The (browser of the) user is (automatically) redirected to the SCZ component SaToSa
- If necessary, a Where-Are-You-From-screen is presented so the user can select the IdP where he/she wants to authenticate
- After the optional WAYF, the user is directed back to SaToSa
- 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)
- 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
- If the IdP has provided an EPPN, SaToSa searches a database the SCZ component COmanage has provisioned and uses EPPN and entity id 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.
- SaToSa can be configured to show a Consent form. If so configured, a consent form is shown
- Whether or not and for what attributes the user consents is returned to SaToSa
- If consent was given (or configured not to be required) SaToSa combines the attributes received from the IdP and from COmanage and supplies the attributes to the service.
- 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 .