Date Model Elements

The Registry Identifier data model is intended to record Identifiers associated with an Entity, including both Identifiers generated and managed by Registry, and Identifiers that are obtained from other sources.

Default Identifier Type

When adding a new Identifier via the UI, it is possible to set the default value for the Identifier type via Configuration > CO Settings.

Login Identifiers

Login to Registry is based on Identifiers that are flagged for login that are attached to People. More specifically, when someone tries to access the Registry application,

  • $REMOTE_USER is examined for an identifier.
  • Registry looks for active Identifiers attached to active Person records across all COs.
  • If at least one active Identifier is found, the user is granted access to the associated COs.

Because Registry does not know the type of the identifier passed via $REMOTE_USER, any Identifier record with a login flag will match this search. Care should be taken if multiple Identifier Types can be used for login to avoid potential conflicts, including potentially across COs.

Identifier Uniqueness and Reassignment

An Identifier must be unique for the entity type within the CO (AR-Identifier-2). By default, Identifier Uniqueness is case sensitive (so e123 and E123 are considered different), however this behavior may be changed by changing the Case Insensitive setting on the Identifier Type definition.

An Identifier can be reassigned if the original Identifier was deleted (as opposed to being set to Suspended status). To avoid having Identifiers reassigned set the status of Identifiers that are no longer needed to Suspended. (AR-Identifier-3, CO-1265)

See Also

Changes From Earlier Versions

As of Registry v5.0.0

  • The login flag only applies to Person, not ExternalIdentity.


  • No labels