...
Use Case 3: Student has system account linked to University account, and wants to use University account to apply to other institutions
More to follow.
Use Cases that describe consumption of identities
Use Case C1: Attribute aggregation with single sign-on
When a student logs in to a service provider using their system credentials, they are initially directed to the system to perform authn duties. The system will verify the user's identity and return their unique identifier. The service provider will then take the unique identifier to the local identity provider, where additional 'enriched' attributes can be found.
Questions:
- In Use Case 2, is it possible that the participant's account creation process acquires the unique identifier and registers the student with the system even if the student does not yet get a system username and password?