...
Guest System/Social Identity Use Cases
- Social Identity Generic Use Cases (See https://spaces.at.internet2.edu/display/socialid/GenericUseCases)
- Social Identity Campus Use Cases (See https://spaces.at.internet2.edu/display/socialid/ Use + Cases)
Guest System
...
Specific (Non-Social Identity) Use Cases
Guest or Affiliate with Sponsored Access to Higher Risk Resource: A non-member subject requires access to a resource that has a higher risk of exposure and consequently requires a higher Level of Assurance (LoA).
Guest or Affiliate that must have Verifiable Contact Information:
Case 1: An affiliate working in a non-university position (private corporation, research organization, etc.), located within the campus boundaries requires a university proximity card for access to their building. They may or may not be required to authenticate to any campus resources. The University needs to have accurate location and contact information and know "when" this affiliate leaves employment so that the prox-card can be deactivated. (Guest/Affiliate System of Record)
Case 2: An affiliate working in a non-university position (private corporation, research organization, etc.), located within the campus boundaries is required to file HazMat reports with the Environmental Health & Safety department.
Guest or Affiliate in "Transitional" Role is issued a Campus Identifier: In some transitional roles, a subject might still be an affiliate of the university but with the expectation that they will become a student or employee in the near future. This is not the traditional "applicant" affiliation in a normal student/employee life cycle, but one where there is a reasonable expectation that the subject will become a campus "member". Examples might include a potential student in a summer program, a "trainee" or a potential employee in a probationary or temporary assignment. In order to make the transition into the Student or HR system easier, a Guest System is used to capture identity information (Guest System of Record)
...