From 282227fda66d7f3e74abd96e067de74e82a55cf8 Mon Sep 17 00:00:00 2001 From: Keith Hazelton Date: Fri, 9 Apr 2021 07:52:00 -0500 Subject: [PATCH] Update person-identifiers.adoc --- person-identifiers.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/person-identifiers.adoc b/person-identifiers.adoc index dd65d06..b4b2737 100644 --- a/person-identifiers.adoc +++ b/person-identifiers.adoc @@ -33,7 +33,7 @@ Match API backend is just a database that understands ref id and sourceID, rovis Person identifiers indicate a single person in a system, but any attribute unique to the person can serve as an identifier for search queries: E.g., email, name, LoginID,... + Grouper external users: ePPN serves as the identifier in the subject source + -- *midPoint:* OID is permanent, not shared name is a name-based identifier (other could be added), can change if needed, could be a campus id that users tend to know + +- *midPoint:* OID is the internal identifier in midPoint - syntax is like a uuid. OID is permanent, not shared; NAME is a name-based identifier (other could be added), can change if needed, could be a campus id that users tend to know + globally unique by inclusion of a scope element or domain identifier + mP can generate any other unique id and share with external systems +