People planning

Edit online

For the people in your organization, you can plan how to import identity records that create IBM Verify Identity Governance users and how to provide their passwords.

The following table includes examples of initial conditions and first implementation steps that administrators might take.

Table 1. Summary of potential user planning issues
Topic Initial condition and questions Example implementation steps
Identities 1 administrator account named itim manager exists with an initial password of secret.
  • Which identity records require IBM Verify Identity Governance user IDs?
  • Does your early implementation need to define more administrators?
 At a minimum, create 1 identity to test each group that IBM Verify Identity Governance provides. Additionally, create another administrative user ID to guard against accidental loss of access.
Import identity records A global identity policy exists.
  • Which data format does your organization plan to use to import identity records?
  • Are the attributes that the global identity policy specifies appropriate for your use?
 Determine which identity feed to use and ensure that the appropriate attributes are specified in an identity policy.

For most organizations, manually loading user data is not a practical method to define many users.
Policies (password, identity) Password policy or forgotten password specifications do not exist. Password synchronization is on.

The default identity policy is based on the uid attribute of the user. If the uid attribute has a null value, the identity policy concatenates the initial of the given name of a person with the surname of a person.

What are the requirements of your organization for a password policy, challenge-response authentication, and identity policy?

 Determine the password policy of your organization. Also, determine challenge-response authentication, and identity policy and then specify these policies.