Skip to end of metadata
Go to start of metadata

Overview of "Manage ION Users" Use Case

Establish ION-wide policies and capabilities to manage users.

Tip: Key Points
UC Priority= 4 or 5: Critical, is in R2
Only boldface steps are required
<#> before a step —> lower priority
(optional) —> run-time option

Related Jira Issues:   Open   •   All


Refer to the Product Description and Product Description Release 2 pages for metadata definitions.

Actors Registered User, Anonymous Guest, Integrated Observatory Operator
Uses UC.R1.01 Hello User
Is Used By  
Is Extended By  
In Acceptance Scenarios None (add to AS.R2.01C Operate Integrated Observatory Network)
Technical Notes  
Lead Team COI
Primary Service Identity and Policy Management Services
Version 1.3.1
UC Priority 4
UC Status Mapped + Ready
UX Exposure ONC


This information summarizes the Use Case functionality.

Manage users and related information in the primary Integrated Observatory. Manage multiple login identities associated with one Integrated Observatory user ID; authenticate requests to link accounts. Manage multiple profiles for one user ID. Perform user registration using selected profile, and assign associated access privileges.


  • Integrated Observatory is managing users in this Release.

Initial State

Individual is Registered User of the Integrated Observatory with another account (as yet unknown to the Integrated Observatory) at a federated organization (e.g., Google).

Scenario for "Manage ION Users" Use Case

  1. Registered User starts to log in or register using CILogon.
    1. Either case may result in same outcome behavior.
  2. Registered User successfully registers under a new external account.
    1. The certificate from the new account is returned to the Integrated Observatory
  3. Upon recognizing that certificate is not known, the Integrated Observatory provisionally assumes this is a new user.
    1. This is the most likely and best default assumption.
    2. Identification of common account information after ION member profile is entered can lead to following path.
  4. The Integrated Observatory assigns the user the appropriate default role and presents a new member profile screen.
    1. This solicits member profile information collection, if following path option is not chosen.
    2. So far, this is path an Anonymous Guest would follow.
  5. The Integrated Observatory also presents the user with additional option(s) to link new account to existing account.
    1. Main option is to link to the existing account ('takes a few minutes').
    2. Another possibility is to continue working as new user, and link to existing accounts later.
  6. Registered User asks to link to existing account, specifying the account name.
    1. The Integrated Observatory generates email to that account, which must be confirmed by clicking on a link in (or entering a code from) that email.
    2. A list of all account names is not offered for privacy reasons.
    3. If a reasonably likely account name (or names) can be suggested, this may be acceptable and is a valuable simplification for the user.
    4. Successful completion of task causes Integrated Observatory to link each account to the other.
    5. Unsuccessful completion — for example, because previous account is no longer accessible to user — must be mediated by Integrated Observatory Operator, who must confirm identity of the two account holders is in fact the same.
  7. Integrated Observatory Operator receives any request for mediation when previous credential account can not be accessed.
  8. Integrated Observatory Operator ascertains relationship of the two accounts, and establishes account linkage if appropriate.
    1. Can involve Registered User providing personal information only known to holder of previous account; call-back to numbers or email to addresses associated with previous account; or a waiting period while attempts are made to contact holder of previous account.
  9. <3> Once account linkage is established, Integrated Observatory offers Registered User the option of disabling the previous account registration.
    1. If user agrees, previous account is flagged so user can no longer use its credentials to log in.
  10. <3> Integrated Observatory Operator reviews status of all newly linked accounts.
    1. Requires display of all user accounts that have been linked since last review/given day.
    2. Suspicious linkages are reviewed by Operator.
  11. <3> For each actual user, multiple credential accounts can be supported, dereferenced to single user.
    1. Single user does not necessarily mean only one profile, but that is the most common scenario.
  12. <3> A Registered User indicates desire to have multiple operational profiles.
    1. An operational profile can represent different metadata about the user, as well as different ION Roles. ION Roles constrain what users can, and can not do, in the Integrated Observatory system.
    2. An example scenario is an operator who is also a normal system user. It is important for such a user to take on the administrator role only when performing administrative functions.
  13. <3> Integrated Observatory presents an interface allowing specification of the new profile.
    1. In most cases, the principal difference may be the role(s) taken on by the user.
    2. Requests for different profiles that are merely presenting different information (e.g., a teacher profile vs a researcher profile) typically would not require any approval authority.
  14. <3> The Integrated Observatory accepts the new specification and, if necessary, routes it for approval to the appropriate role.
    1. The Integrated Observatory Manager is the initial role with this responsibility.
  15. <3> The system notifies the user of the results of the request, once the Integrated Observatory Operator takes action on it.
    1. This is following the form in the Conduct Negotiation use case.
  16. <2> Once granted a new profile, the user may switch profiles at will, while remaining logged in.
    1. It may be valuable to associate different profiles to credential accounts eventually, as users demand it.

Final State

The Registered User is associated with the new credential account. The user has an additional role in a new profile if it is appropriate, or a response indicating why it is not appropriate.


These comments provide additional context (usually quite technical) for editors of the use case.

(click on # to go to R2 use case)
01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20
21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40
41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
61     27B


r2-usecase r2-usecase Delete
usecase usecase Delete
productdescription productdescription Delete
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.