HAI Use Case: User securely authenticates and gets a secure session: Difference between revisions
(New page: {{subst: Template:Use Case}}) |
No edit summary |
||
Line 1: | Line 1: | ||
'''Point Of Contact:''' '' | [[Category:HAI]] | ||
'''Point Of Contact:''' ''[[User:ndp | Nathan Potter]]'' | |||
== Description == | == Description == | ||
A user authenticates with a Hyrax server and gets a secure session. | |||
== Goal == | == Goal == | ||
Provide user identification information to Hyrax/Tomcat in order to allow Hyrax Admin's to manage access to datasets. | |||
== Summary == | == Summary == | ||
* A user attempts to access a seurce part of the Hyrax server. | |||
* The server presents an authentication challenge. | |||
* The user provides credentials. | |||
* The user is granted secure access. | |||
== Actors == | == Actors == | ||
* User - typically software, either an automation or something driven by a human (like a browser) | |||
* Hyrax | |||
== Preconditions == | == Preconditions == | ||
* The user want to access secure data held in a Hyrax server. | |||
* The Hyrax server has been configured to consider this data secured. | |||
== Triggers == | == Triggers == | ||
The user attempts to access the secured data set on Hyrax. | |||
== Basic Flow == | == Basic Flow == | ||
# A user attempts to access a secureds part of the Hyrax server. | |||
# The server returns an authentication challenge. | |||
# The user provides credentials. | |||
# The user is granted secure access. | |||
== Alternate Flow == | == Alternate Flow == | ||
# A user attempts to access a restricted part of the Hyrax server. | |||
# The server returns an authentication challenge. | |||
# The user provides credentials. | |||
# The user is denied access. | |||
== Post Conditions == | == Post Conditions == |
Latest revision as of 18:52, 9 November 2010
Point Of Contact: Nathan Potter
Description
A user authenticates with a Hyrax server and gets a secure session.
Goal
Provide user identification information to Hyrax/Tomcat in order to allow Hyrax Admin's to manage access to datasets.
Summary
- A user attempts to access a seurce part of the Hyrax server.
- The server presents an authentication challenge.
- The user provides credentials.
- The user is granted secure access.
Actors
- User - typically software, either an automation or something driven by a human (like a browser)
- Hyrax
Preconditions
- The user want to access secure data held in a Hyrax server.
- The Hyrax server has been configured to consider this data secured.
Triggers
The user attempts to access the secured data set on Hyrax.
Basic Flow
- A user attempts to access a secureds part of the Hyrax server.
- The server returns an authentication challenge.
- The user provides credentials.
- The user is granted secure access.
Alternate Flow
- A user attempts to access a restricted part of the Hyrax server.
- The server returns an authentication challenge.
- The user provides credentials.
- The user is denied access.
Post Conditions
Here we give any conditions that will be true of the state of the system after the use case has been completed.
Activity Diagram
Here a diagram is given to show the flow of events that surrounds the use case.
Notes
There is always some piece of information that is required that has no other place to go. This is the place for that information.
Resources
In order to support the capabilities described in this Use Case, a set of resources must be available and/or configured. These resources include data and services, and the systems that offer them. This section will call out examples of these resources.
Resource | Owner | Description | Availability | Source System |
name | Organization that owns/ manages resource | Short description of the resource | How often the resource is available | Name of system which provides resource |