Use Case:  User Authenication.

Note that authentication of user ID is not the same as granting permission to access any particular information in the archive.

Goal: Confirm a user with a particular user ID has permission to access the archive

Contact Author: G.Fuller

Role(s)/Actor(s):

Primary: Any ALMA subsystem
Secondary: Executive, UserAdmin

Priority: Critical

Performance: Low

Frequency: Minutes

Preconditions: 

  1. Archive is running

 Basic Course: 
  1. Subsystem requests connection to the archive (XMLStore), for a human user there is an user interface which acts as a subsystem.
    Alternate Course: none
    Exception Course: Connection can't be established: try again until timeout.
    Postcondition: Connection established.
  2. Subsystem sends user authentication data (user ID) to archive.
    Alternate Course: None.
    Exception Course: Authentication failed: This is a fatal exception! Close connection.
    Postcondition: Connection established.
Postconditions: 
  1. User connected to archive.

Issues to be Determined or Resolved: 

The communication of the user ID and the associated permissions have to be clarified. The required level of granularity for permissions has to be specified by SSR and operational requirements.

Last modified: $Date: 2004/09/07 23:03:23 $ by $Author: gaf $