Skip to end of metadata
Go to start of metadata

Document Status

This brick is due for review. Scanning the environment may reveal new, unantipated integration solutions (e.g. Canvas).

Description

Person Data Integration is a set of technologies used by customer applications to consume data about a person or persons.

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:

  • Elastic Cache & PWS

Protocols:

  • none designated

Technical Services:

  • Person Event Producer
  • Microsoft Graph

Software:

  • TIER software

Protocols:

  • none designated

Technical Services:

  • TIER API

Software:

  • none designated

Protocols:

  • none designated

Technical Services:

  • none designated

Software:

  • Shibboleth Service Provider
  • Kuali Identity Management (KIM)

Protocols:

  • REST
  • SAML 2.0
  • SQL

Technical Services:

  • Person Web Service (v1 resources)
  • UW Shibboleth Identity Provider
  • UWWI Active Directory
  • UW Directory
  • Kuali Identity Management
  • Operational Data Store

Software:

  • Mango MDS C libraries
  • Mango MGO C libraries

Protocols:

  • Mango protocol
  • LDAP

Technical Services:

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

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. With more evaluation a Person Event Producer may be designated the strategic replacement to some technologies, since event-driven architecture (EDA) is emerging as a baseline data integration pattern.
    2. Microsoft Graph (prior Windows Azure Active Directory Graph API) hasn't been evaluated for strategic fit. It may emerge as a strategic and future baseline technology option for some use cases.  Microsoft Graph is where Microsoft is investing their efforts and it will be getting features that Azure AD Graph will not be getting.
  • Strategic
    1. TIER (Trust and Identity for Education and Research) is developing a set of APIs for integrating person data into applications. Further evaluation of the APIs and possible software implementations are needed to clarify the strategic direction of options.
  • Tactical
    1. None designated.
  • Baseline
    1. None designated.
  • Containment
    1. Mango technologies are under containment and for internal use only.
    2. Although use of the Person Directory Service via LDAP is in use by many services we have been encouraging new integrations to use PWS via REST where possible.  New person attributes would be added to PWS and not made available via PDS.
    3. Person Registry Source Web Service (PRSWS) will be scheduled for retirement in the near future.
  • Retirement
    1. None designated.

References

See Also

Last Review Date

August 15, 2016