Topic # | Requirement |
ID-1 | Maintain a central data repository that uniquely identifies entities (individuals/organizations) |
ID-2 | The unique identifier (UFID) is never re-issued to a different entity. |
ID-3 | Provide Identity search-match capabilities |
ID-4 | Provide Identity merge/ID resolution capabilities |
ID-5 | Maintain UFID record statefulness (i.e., active, inactive, error) |
ID-6 | Provide notification functionality to entities/units of changes to selected attributes |
ID-7 | Provide basic workflow capabilities for review and approval of selected changes |
ID-8 | Provide ability to publish changes to subscribing service providers |
ID-9 | Provide interface to postal validation, standardization and formatting services |
ID-10 | Support multi-national formats for phones, addresses, etc. |
ID-11 | Provide or support a scheduled event processor |
ID-12 | Support multiple credentials |
ID-13 | Support multiple identifiers |
ID-14 | Support effective dated values (i.e., start and end dates for affiliations, addresses, etc) |
ID-15 | Support and interacts with identity federation to internal/external service providers |
ID-16 | Support the InCommon Identity Federation standards and protocols |
ID-17 | Support SOAP messaging to other IAM components and service providers. |
ID-18 | Support REST-based web service interfaces |
ID-19 | Support an ESB (Enterprise Services Bus) for communication (e.g., BizTalk) |
ID-20 | Support the eduPerson, eduOrg and eduCourse Internet2 MACE standards |
ID-21 | Support a file/batch interface for importing data, including support for XML, CSV, .xls, fixed width, and other formats |
ID-22 | Support a file/batch interface for extracting data, including support for XML, CSV, .xls, fixed width, and other formats |
ID-23 | Provide a management interface (UI) for authorized registry authorities (Identity Coordinators, Administrators) to manage information in the data store. |
ID-24 | Provide a management interface (UI) for administrative troubleshooting and configuration |
ID-25 | Provide a set of APIÕs (SOA, SOAP, REST, etc.) for programmatic interaction with the registry along with security for authorized access |
ID-26 | Maintain a permanent audit log/history of ALL activities/events within the data store (adds, changes, deletes) with record of entity making changes with timestamps and comments |
ID-27 | Provide a UI to the audit log/history of ALL activities/events along with reporting capability |
ID-28 | Support a self-service user interface (UI) to change selected registry attributes |
ID-29 | Provide services to add, update and archive persons |
ID-30 | Provide services to add, update and archive address information for a person |
ID-31 | Provide services to add, update and archive email address(s) information for a person |
ID-32 | Provide services to add, update and archive emergency contact information for a person (who to contact) |
ID-33 | Provide services to add, update and archive name information for a person |
ID-34 | Provide services to add, update and archive telephone number information for a person |
ID-35 | Provide services to add, update and archive net id information for a person |
ID-36 | Provide services to add, update and archive credential information for a person |
ID-37 | Provide services to add, update and archive Identity Assurance information for a person |
ID-38 | Provide services to add, update and archive affiliation information for a person |
ID-39 | Provide registry attributes that can be entered or computed based on other existing registry attributes. |
ID-40 | Provide multiple levels of privacy and publishing indicators/attributes/flags |
ID-41 | The data model should support unlimited new categories and/or types of names, addresses, phone numbers, emails, identifiers, relationships, locations, etc. See Appendix B for logical ERD diagram. |
ID-42 | Identity proofing to support NIST Level 2 |
ID-43 | Logging and management of Identity Proofing |
ID-44 | Data driven attribute definition of all >>>> entity object types. |
Overview
Content Tools