An External Identity is intended to represent any sort of identity external to the CO. Common examples of External Identities include

  • Federated Identities
  • Social Identities (Google, Facebook, etc)
  • Research Identities (ORCID)
  • ERP Records (PeopleSoft, Workday, Banner)

Date Model Elements

In general, External Identities and External Identity Roles track People and Person Roles.

External Identities as reflected in Registry are considered read-only, changes must be made in the System of Record any sync'd back to Registry.  External Identity records are not intended to be provisioned - they are an intermediate representation of the System of Record data and are intended for Registry Administrator use only. However, the Person record attributes generated from External Identity records may be edited, and may furthermore be frozen to preserve local overrides.

Searching External Identities

Currently, External Identities are not searchable as part of Global Search.

In v4, it was possible to list and filter all Organizational Identities since they were top level objects linked directly to the CO and could exist on their own. In PE, External Identities are a part of the Person record, and as such there is no directly equivalent view. A somewhat similar result can be obtained by filtering External Identity Source Records, available via ALL > Artifacts > External Identity Source Records.

See Also

Changes From Earlier Versions

As of Registry v5.0.0

  • OrgIdentity was split into ExternalIdentity and ExternalIdentityRole.
  • ExternalIdentity directly relates to Person (a Person may have multiple External Identities, but an External Identity can only belong to one Person). The CoOrgIdentityLink crosswalk has been eliminated and Organizational Identity Pooling support has been dropped.
  • affiliation was replaced with affiliation_type_id.
  • o was renamed organization.
  • ou was renamed department.
  • External Identities no longer have Primary Names.
  • No labels