Skip to content

Commit

Permalink
Update person-identifiers.adoc
Browse files Browse the repository at this point in the history
  • Loading branch information
khazelton authored Apr 9, 2021
1 parent 71bdfc7 commit 5589379
Showing 1 changed file with 9 additions and 9 deletions.
18 changes: 9 additions & 9 deletions person-identifiers.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -23,19 +23,19 @@ https://wiki.shibboleth.net/confluence/display/CONCEPT/NameIdentifiers
==== Unique across the IdPs population Y/N?

- *COmanage*, external identifier are tuples: {Identifier for the external source, PersonID assigned by that source}
- Enter ePPN, or link in email for new ppl being added
- COmanage: In general, a multi-values list of identifiers paired with a source identifier; there is a non-shared internal ID
- Refereence ID: two match modes: Match up front; config. COmanage to match based on RefID. registry gets a ref id, and stores it
- Match API backend is just a database that understands ref id and sourceID, rovision to LDAP, point Grouper subject source at LDAP;
Enter ePPN, or link in email for new ppl being added +
COmanage: In general, a multi-values list of identifiers paired with a source identifier; there is a non-shared internal ID +
Refereence ID: two match modes: Match up front; config. COmanage to match based on RefID. registry gets a ref id, and stores it +
Match API backend is just a database that understands ref id and sourceID, rovision to LDAP, point Grouper subject source at LDAP


- *Grouper* defines "id" as person identifier and "identifier" as potentially anything that can uniquely identify a person
- 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
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
- globally unique by inclusion of a scope element or domain identifier
- mP can generate any other unique id and share with external systems
- *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 +
globally unique by inclusion of a scope element or domain identifier +
mP can generate any other unique id and share with external systems +


==== name-based or otherwise recognizable? Y/N
Expand Down

0 comments on commit 5589379

Please sign in to comment.