1. Central Login for PPP* *Pittsburgh Personalized Portal
Michael V. Yudelson
PAWS Meeting on

2. Motivation The number of adaptive applications provided by PAWS grows
Most applications maintains user model
Almost all store user credentials etc.
Users prefer to have ONE login/password
Storing user identities centrally – logical, saves efforts, proven to be practical
Michael V. Yudelson (C) 2006

3. Note User identity ≠ User model/profile
Central store is not intended for application specific information
If you do not directly use some information about the user, why should you collect it and/or maintain it?
Michael V. Yudelson (C) 2006

4. What’s User Identity? Mandatory fields Recommended fields
Name: Last, First M.I.
Login
Password – digested
Recommended fields
Optional Fields
Organization, City, Country, How did you learn about us
Anything else?
Michael V. Yudelson (C) 2006

5. What else? Groups Group-User links Group Name
Michael V. Yudelson (C) 2006

6. What’s CUIS can do for you
ADAPT2 integration
Adding new users to existing groups
Checking user credentials and issuing Session ID for modeling users on CUMULATE2
Michael V. Yudelson (C) 2006

7. What you can do for CUIS Provide information about your users
Do not duplicate users in your database (otherwise what’s the point)
Instead reference user identities by URI
URI=namespace+login
Michael V. Yudelson (C) 2006