How to identify users, people and accounts within Dataporten.
Dataporten is not locked down to operate on only one kind of user identificator. Each user record is issued a unique transparent primary UserID, and a set of secondary userIDs of various kinds.
The primary user identifier is generated for users the first time they access Dataporten. It is in the UUID format, and is opaque, not releasing any additional information about the user. It is intended to be longterm, surviving merging of schools and universities.
For now, Dataporten will not perform automatic account mapping between user accounts.
Dataporten can handle generic secondary userIDs in different namespaces. In example, Dataporten handles both national identity numbers and Feide IDs.
One user may have several secondary userIDs, even of the same type (prefix). It is important that application developers take this into account when implementing applications.
National Identity number
Right now, Dataporten is only configured to operate with national identity numbers when the user is logging in using ID-porten. If the application is granted the sufficient scopes to access the national identity number, it will look like this:
Merged primary keys
If two user records are merged at Dataporten, one entry will be removed and all userids from this record will be copied into the primary record. The primary key of the removed record will be added as a secondary historic key to the primary record.
Applications that obtains the primary userID from Dataporten, will always also get access to historical primary keys like this: