Implementing Custom Actions for Password Self-Change on DYN Endpoints in Novell eDirectory

Products

• CA Identity Manager
• CA Identity Governance
• CA Identity Portal

Issue/Introduction

Identity Manager administrators managing Novell eDirectory endpoints may face issues where password self-change events are not synchronized correctly with the passwordExpirationTime attribute. This article provides steps to implement a custom operation binding that distinguishes between administrative password resets and user-initiated self-changes, ensuring the passwordExpirationTime is updated accordingly.

Environment

Identity Manager 14.5

Cause

By default, the Identity Manager Provisioning Server does not distinguish between administrative and self-initiated password changes on certain DYN endpoints. Native changes intercepted by the Password Synchronization Agent do not automatically trigger an update to the Novell eDirectory passwordExpirationTime attribute, causing the newly changed password to remain in an expired state.

Resolution

Follow these steps to configure a custom action that updates the passwordExpirationTime attribute:

1. Configure Endpoint Metadata

   1. Open Connector Xpress, right-click your DYN endpoint, and select Edit metadata.
   2. Navigate to Data Model tree > Classes > eTDYNAccount > Properties.
   3. Click Add and define the following property:
      • Name: eTSelfChange
      • Type: Integer
   4. Add metadata to the new property:
      • isHidden: Type: Boolean, Value: true
      • beanPropertyName: Type: String, Value: !eTSelfChange!
      • connectorMapTo: Type: String, Value: !eTSelfChange!
   5. Save the metadata and export the Data Model XML.
   6. Go to Metadata > Merge, select the XML file, choose Overwrite, and click OK.
   7. Save the Connector Xpress project.

2. Define Operation Binding

   1. In the User Account object class, define a new Operation Binding:
      • Type: Script
      • Operation: Modify
      • Timing: Instead of
      • Global Script: Load contents from doCustomModify.txt
      • Function Name: doCustomModify
   2. Save the project and re-deploy the metadata.

If issues occur during deployment, monitor the jcs_stdout.log for debug messages generated by the doCustomModify function to identify errors in the mapping or script execution.

Additional Information

To speak with a customer representative or a Support Engineer see Contact Support. Scroll to the bottom of the page and click on your respective region.