Rutgers Institutional Use Cases

Owned by Benn Oshrin
Last updated: Jul 16, 2010 by Jeremy JeremyVersion comment

Rutgers

  1. Identities for populations not currently in the identity management infrastructure (Rutgers-1)
  2. Fast identity creation for new hires (provisional hire) (Rutgers-2)
    1. Includes policy on who is authorized and maximum "good until" date
  3. Real-time System of Record (SOR) data where SOR is capable, batch otherwise (Rutgers-3)
  4. Guest sponsorship (Rutgers-4)
    1. Short-term visitor
    2. Long-term service consumer
    3. Bulk import (eg: from .xls)
    4. Federated Guest Management (eg: via OpenID) (Guests Use Case)
    5. Local Guest Management (eg: via OpenID) (Guests Use Case)
  5. Identity lifecycles (Rutgers-5)
    1. Role Lifecycle (student -> staff -> alumni)
    2. OpenID -> NetID
    3. Admissions - (Apply, Admit, Enroll -graduates admissions,undergraduates admissions)
  6. Directory construction, including real-time updates, multiple job titles, and "vanity" titles (and other data, inc email addresses) (Rutgers-6)
  7. Group management, including manual and dynamic (business rule generated) (Rutgers-7)
  8. Provisioning/deprovisioning (Rutgers-8)
    1. Direct callout
    2. RATS
    3. XML standard?
    4. Lock/unlock an account
  9. Data dictionary and versioned attribute definitions (Rutgers-9)
  10. Password trust/levels of assurance (Rutgers-10)
  11. ID Card (RUConnection) integration (Rutgers-11)
  12. Activation Keys (Rutgers-12)
    1. Could include 20 questions for credential reset
  13. Roles and role specific data (Rutgers-13)
    1. Chair of department X
    2. Number of course X
    3. Department phone number
  14. Data Normalization (Rutgers-14)
  15. Password management (Rutgers-15)
    1. Establish, reset, change password
  16. Guest account provisioning, deprovisioning, renewal (Rutgers-16)
  17. OR as the SOR (Rutgers-17)
  18. Privacy policy enforcement (Rutgers-18)
    1. Ability to suppress records or portion of records as per FERPA or user request
    2. Ability to override suppression on a per-approved-application basis
  19. Split NetID from UNIX context (Rutgers-19)
  20. Audit all changes that are applied to a person (Rutgers-20)
  21. Tools for support staff and administrators (Rutgers-21)
    1. Perhaps also "policy and best practices"/deployment guide
    2. Ability to "impersonate" users for debugging/analysis purposes

Use cases targeted for R1: 1, 4, 5, 6, 9, 14, 20, 21

Additional considerations:

  1. Splitting authentication from authorization
  2. Reducing the number of usernames and passwords people have
  3. Identifier consolidation (IID vs NetID vs RCPID vs RUID, etc)
  4. Improving HR and SIS data entry processes, especially wrt reconciliation