Distinguished Name attribute value returns null in Identity Manager
search cancel

Distinguished Name attribute value returns null in Identity Manager

book

Article ID: 445848

calendar_today

Updated On:

Products

CA Identity Suite

Issue/Introduction

Introduction

When attempting to retrieve the User Distinguished Name (DN) attribute value via Policy Xpress (PX) or a standard task, the value returns as null or empty. This occurs even when the attribute is mapped in the directory configuration.

Symptoms

  • Policy Xpress (PX) triggered 'After - Create User' returns an empty string for the DN attribute.
  • The User DN field appears blank in 'Modify User' screens.
  • Standard user.getAttribute('dn') calls in custom logic return null.

Environment

  • CA Identity Manager 14.x, 15.x
  • Symantec Directory (User Store)

Cause

In Symantec Directory and Identity Manager architecture, the dn (Distinguished Name) is the unique identifier (RDN) of the object and is not defined as a standard profile attribute within the user object itself. Therefore, it cannot be retrieved using standard attribute fetch methods or schema extensions.

Resolution

To retrieve the DN value for use in Identity Manager tasks or Policy Xpress, implement a Business Logic Task Handler (BLTH). A BLTH can access the full DN via the provider interface.

  1. Create a custom Java class extending BLTHAdapter.
  2. Use the UserProvider to locate the user and retrieve the unique name.
  3. Example code snippet for retrieving the DN:
java
 
String userUniqueName = blthContext.getUser().getUniqueName();// This returns the full DN of the user object in context
  1. If the value is needed for a specific screen field, set the attribute in the handleValidation or handleSetSubject method:
java
 
blthContext.getUser().setAttribute("customDnDisplayAttribute", userUniqueName);
  1. Compile and deploy the BLTH to the Identity Manager environment.

For detailed implementation steps, refer to the .

Additional Information