Model Name :

Use of Existing Identity, University credentials, to access vendor resources supporting personalization

Description of the Assumed Model:

Many vendors support a personalized experience for users; allowing them to set preferences and save searches. This personalized experiences requires the users to create a userid and password with the vendor.

Using existing credentials, like University credentials is the preferred method of access. The eliminates the need for the user to remember yet another userid/password and supports SSO to vendor supplied resources.

Model Use Cases (Basic) :

1. Use Case Name :

• Refworks

   Use Case Description :

• Refworks requires the creation of a userid/password for each user accessing the site. The site is used to manage citations; uploading bibliographic data, creating bibliographies. The citation data uploaded must be associated with an account at Refworks.

• University IDP authenticates userid/password and releases primary user identifier (eppn) to Refworks. First time use of eppn at Refworks creates the Refworks account; subsequent accesses Refworks account.

• access to SSO protected resource from
      -- on campus
      -- off campus( ie. from home, while traveling)

   Primary actor(s) :

• Members of the community (sometimes referred to a a Library Patron, but that term sometimes has a narrower meaning)

   User Type :

• End User

   Technology Type :

• N/A

   Vendor Type :

• N/A

   Precondition :

nbsp;nbsp; Trigger:

• Patron attempts to access Refworks

nbsp;nbsp; Basic Flow:

• Via web browser, patron attempts to access resources. Access to resources is granted.

Model Use Cases (Advanced) :

1. Use Case Name :

   Use Case Description :

   Primary actor(s) :

   User Type :

   Technology Type :

   Vendor Type :

   Precondition :

   Trigger :

   Basic flow :

   Alternate flow(s) :