- See also: COmanage / Enterprise Entity Registry Gap Analysis
Excerpt |
---|
TIER Entity Registry Requirements Not Met by COmanage 1.0.2 Compared to the TIER Entity Registry Requirements |
- COmanage Registry 1.0.2 (note: Handle (some) Gaps via a plugin architecture of Comanage, some however are not solvable in this manner per Benn O)
- Lacks public APIs by which System of Records can 1) notify the Registry of persons that are new to the SoR and 2) persist relevant SoR-sourced person information in the Registry
- Currently Account management is a POC only, more effort seems to be required to move this past the POC stage
- . external vs internal provisioning needs to be expanded and enhanced
- Batch / File Processing : inbound formats able to be defined as a future feature... currently lacking in following areas:
administration
capability for proxy/delegate on attribute of self service out of box
bulk loading - half way there
enterprise vocabulary at UI - needs noodling and review.
Person
lifecycle
mulitple roles
self selcted netid (not available)
data privacy - considerations (not there)
enroll via console operation then HR or whatever bringing those together have opportunities to improve
MatchingId
Proofing - what is to be tracked, VO typically not doing this, role to credential management maybe
Provisioing
...