...
Participation in Building the User's Representation in the AdmitMe Ecosystem
In order to take advantage of AdmitMe, an individual will gradually assemble identity information at service organizations that are participants in the AdmitMe project. This identity information will be keyed by the user's central AdmitMe identifier.
First, any participant may decide to use only AdmitMe for login. Second, a participant may choose to offer both local accounts and AdmitMe for login. A third choice envisions permitting login from any InCommon member. These three strategies are described below.
In each integration strategy, there is a consistent, shared AdmitMe identifier. User information is not stored centrally, but is instead stored at each service organization.
The choice of integration strategy is the sole province of each participant, and all three strategies can co-exist. Each participant is encouraged to choose the integration strategy that best suits their needsDuring the November 4 technical committee teleconference there was much discussion about the various flows a student may take to register through the system. Basically, the discussion broke into two general categories which need to be described.
Integration Strategy 1: The
...
Service Organization Relies on AdmitMe for All Authentication
Integration strategy 1 presents a user with a single login choice: AdmitMe. This removes the need for the service organization to manage the authentication of users, a costly and time-consuming process. It also greatly simplifies the user experience.
After clicking login, the user will be sent to AdmitMe and In this flow, the first place a student goes will be the system's home page. The student will be shown the logos for all the various participants in the system, and will learn how a single system account will Federate their identity and provide single sign on to some or all of each participant's offerings. The student will create a system account at that time, and will be given the option to create identities with each participant.
Participants will only use the system credentials for authentication, and will only keep enriched participant-relevant data locally. The system will provide an identifier that is unique to the student that links all the accounts together.
Integration Strategy 2:
...
Login through AdmitMe or through Local Credentials
This integration strategy reflects both some participant's desires to have local participant credentials and the reality that there may be a migration strategy required for participants who will eventually use Integration Strategy 1. There are 4 different flows through this strategy that are described in further detail.
...