Skip to end of metadata
Go to start of metadata

Document Status

This brick is due for review.

Description

Identity Registration options consist of technologies and processes that allow customers to register identities in the UW Identity Registry (aka UW Person Registry).

Status Table

The following table categorizes related technologies according to their current lifecycle status.

Emerging
(Trends to watch)
Strategic
(Future)
Tactical
(Limited support)
Baseline
(Full support)
Containment
(Reduced support)
Retirement
(Scheduled for retirement)

Software:

  • none designated

Protocols:

  • SCIM

Technical Services:

  • Identity Registration event producer/consumer

Software:

  • CIFER software (PSU CPR, Open Registry, ForgeRock, etc.)

Protocols:

  • none designated

Technical Services:

  • CIFER APIs

Software:

  • none designated

Protocols:

  • none designated

Technical Services:

  • Identity Registration API 1.0

Software:

  • none designated

Protocols:

  • Identity data file from system of record
  • REST 

Technical Services:

  • Identity data file import from system of record

Processes:

  • UW NetID Sponsorship Process 2.0

Software:

  • Mango MDS C libraries
  • Mango MGO C libraries
  • Empnetid COM object
  • Empnetidsignup COM object

Protocols:

  • Mango protocol

Technical Services:

  • Person Registry Source Web Service (PRSWS)
  • Mango API

Processes:

  • UW NetID Sponsorship Process 1.0
  • Manual registration processes (spreadsheets, etc.)

Software:

  • none designated

Protocols:

  • none designated

Technical Services:

  • none designated

Note: Refer to the IAM Brick Reference for complete descriptions of the six status designations and common lifecycle patterns.

Comments

  • Emerging
    1. SCIM (System for Cross-domain Identity Management) may emerge as an open Internet standard for registering identities from systems of record.
    2. Event-driven architecture and event producer/consumer patterns for identity registration may (or may not) emerge as a solution for identity registration. 
  • Strategic
    1. CIFER (Community Identity Framework for Education and Research) is developing a set of APIs for managing registration records in an identity registry. Further evaluation of the APIs and possible software implementations are needed to clarify the strategic direction of options related to identity registration.
  • Tactical
    1. Identity Registration API 1.0 is available for limited use. It is expected to enter baseline status, or a subsequent version.
  • Baseline
    1. Importing data feeds from other systems of record is a baseline solution. As APIs mature and take hold, use of data feeds will be contained.
  • Containment
    1. Mango technologies are under containment and for internal use only.
    2. The empnetid and empnetidsignup COM objects will be scheduled for retirement as HR/Payroll Modernization transitions clients to new technologies. 
    3. Person Registry Source Web Service (PRSWS) will be scheduled for retirement when the Identity Registration API supports the related use cases.
    4. Other registration processes like UW NetID Sponsorship Process 1.0 and manual registration processes (spreadsheets, etc.) will be retired as opportunities arise.
  • Retirement
    1. None designated.

References

See Also

Last Review Date

April 7, 2014

  • No labels