You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

Brief Description

An IdM system is designed to be an authoritative central hub of identity information. External services may access information through APIs or directory services, or data may be provisioned to external services. It is crucial to ensure that information security is maintained when data is in transport and when stored in a new location. Changes in the IdM system should be propagated to external systems in a timely manner. The ease and speed of propagating changes may be a factor when procuring systems which need to be integrated with the IdM system.

Generic Functional Requirements

  1. information about a user should include attributes as specified by the organization
  2. only the IdM system should be able to write to log/audit data stores
  3. the IdM system must be able to associate user account data across multiple systems each having different schemes for local identifiers
  4. the IdM system needs to notify downstream systems of user-related events in a timely and secure fashion
  5. the IdM system must consume upstream user-related events from systems of record in a timely and secure fashion

Standards Support and Integration Considerations

Key Design Considerations

Technical Solutions

Case Studies

Specific Products

  • No labels