Configuring Unique LOGIN_ID and USER_ID Generation with Sequential Counters
search cancel

Configuring Unique LOGIN_ID and USER_ID Generation with Sequential Counters

book

Article ID: 438684

calendar_today

Updated On:

Products

CA Identity Suite CA Identity Manager

Issue/Introduction

Users attempting to create new accounts in CA Identity Suite encounter errors when a user with the same name already exists. The default configuration may not automatically append a unique counter to the LOGIN_ID or USER_ID fields, leading to manual intervention or task failures.

Environment

  • Product: CA Identity Suite / CA Identity Manager
  • Version: 14.x and 15.x

Resolution

To generate a unique LOGIN_ID and synchronize it to the USER_ID field, follow these configuration steps:

1. Configure the User ID Build Handler

Update the format in the User ID Build Handler LAH to meet your business requirements. The format determines how the ID is constructed.

  • OOTB Format Example: %L,3%%F,2%%C,2% (Uses first 3 of Last Name, first 2 of First Name, and a 2-digit counter).

2. Update the Create User Task Profile

To ensure the generated ID is used during the task:

  1. Navigate to the Create User task in the Identity Manager User Console.
  2. Modify the Profile Screen.
  3. Ensure the LOGIN_ID attribute is present and uses the format |LOGIN_ID| to trigger the LAH.

3. Synchronize LOGIN_ID to USER_ID via Policy Xpress (PX)

Since the LAH typically targets the LOGIN_ID, use a PX Policy to copy this value to the USER_ID field before submission:

  1. Policy Type: UI Policy.
  2. Events: On Validate On Submit for the Create User task.
  3. Data Element: Retrieve the value of the LOGIN_ID attribute.
  4. Action: Set the USER_ID attribute using the value retrieved from LOGIN_ID.

4. Ensure Uniqueness for the Initial Entry

To prevent errors during the initial UI validation:

  • Set the USER_ID field to Hidden on the task profile screen.
  • Assign a Static Dummy Value (e.g., TEMP_ID_123) to the hidden field.
  • The PX Policy will overwrite this dummy value with the properly formatted and unique LOGIN_ID before the task is finalized in the data store.

Additional Information

Logical Attribute Handlers in OOTB Environment