...
Central Person Registry (CPR)
...
Pros
...
Cons
- Mature, well-developed product. Now in production.
- Very well documented
- Imposes unique id at the time an individual is enrolled in any system of
...
- record (SOR).
- Has a good identity matching process (identity matching and address normalization software are not open source).
- Has a process that normalizes addresses.
- Business model based on a very tight coupling between Registry and SORs, where Registry generates IDs to be used by SORs. This works well in an environment which supports tight technical and functional owner integration between SORs and IDMS. Can be
...
- challenging to adapt to an environment where SORs are managed outside IAM teams and in technology that does not support real-time integration with IDMS for unique ID generation
...
- .
- All data for an individual is stored in a single set of tables (database) with effective dates and end dates indicating which record is current, historic or future. This might make the check for the current data less intuitive.
- Not yet released as an open source project (this is in progress)
Open Registry
...
Pros
...
- jasig incubator project. Now in production at Rutgers.
- Keeps a set of tables with the data received from the SOR for each individual.
- Current data and historic data are kept separately.
...
- Rutgers has a UI now that does a lot of what we would want to do (even though it is not part of the open source code base)
- Does not assume it is the source of IDs
...
- - can accommodate environment where IDMS consumes and reconciles identities created in SORs
- Identity match is rudimentary
...
- While it is an incubation project of jasig, Rutgers is the only campus that has been contributing for some time and migrating to a community support/development model will take some time and effort.
- It appears that some of the UI that Rutgers is using is not open source and is developed against OpenRegistry directly, and not against the API.
- API will need to be expanded as it currently does not implement all of the functionality that the Rutgers UI can do.