Planning for DirX Identity Connectivity

This chapter provides a planning checklist of the issues that you must take into account when deciding how to deploy DirX Identity Connectivity in your environment.

Planning tasks include:

  • Identify the source systems

  • Decide on source system workflows

  • Identify the target systems

  • Decide on target system workflows

  • Decide on password synchronization

  • Define the system architecture

  • Define system maintenance

Identify the Source Systems

  • What are the source systems that create and maintain identity information?

  • What are the characteristics of the source systems in terms of authentication and authorization?

  • What is the best connected directory template that can be used for source system integration?

Decide on Source System Workflows

  • What is the best workflow template that can be used for source system integration?

  • Is it necessary to set up secure connections?

Identify the Target Systems

  • What are the target systems that must be integrated?

  • What are the characteristics of the target systems in terms of authentication and authorization?

  • How should these target systems be migrated into the DirX Identity Connectivity environment?Can there be an initial load of accounts and/or groups into DirX Identity?

  • Is there a need for virtual target systems?

  • What is the best connected directory template that can be used for target system integration?

Decide on Target System Workflows

  • Which technology shall be used: Java-based real-time workflows or Tcl-based technology or both?

  • What is the best workflow template that can be used for target system integration?

  • Is it necessary to set up secure connections?

Decide on Password Synchronization

  • Which target systems shall be synchronized with the central password solution?

  • What are the possible sources for password changes: the Windows login, a web solution or both?

  • Shall the messaging connections be secured via SSL?

Define the System Architecture

  • How many Identity domains shall be handled?

  • Shall all Identity domains be handled by separate Connectivity domains or do you plan to handle all Identity domains by a single Connectivity domain?

  • Which connections should be secured, for example via SSL?

  • Which attributes are required to be encrypted?

  • Shall your administrative (bind) passwords be encrypted?

Define System Maintenance

  • How often shall your administrative passwords be changed?

  • Define a procedure to change your administrative passwords consistently.

  • What is the interval at which to change your certificates for data and administrative password encryption?

  • Define a procedure to change your certificates from time to time.