Managing "ds-pwp-account-disabled" Oracle Unified Directory (OUD) operational attribute via JNDI Connector

book

Article ID: 6359

calendar_today

Updated On:

Products

CA Identity Manager CA Identity Governance CA Identity Portal CA Risk Analytics CA Secure Cloud SaaS - Arcot A-OK (WebFort) CLOUDMINDER ADVANCED AUTHENTICATION CA Secure Cloud SaaS - Advanced Authentication CA Secure Cloud SaaS - Identity Management CA Secure Cloud SaaS - Single Sign On

Issue/Introduction

When using a ConnectorXpress JNDI-DYN mapped connector to build an Oracle Unified Directory (OUD) connector the operational attribute ds-pwp-account-disabled does not appear as an attribute that can be mapped and managed.

Cause

The operational attributeĀ ds-pwp-account-disabled is not part of the account's objectclass (i.e. inetorgperson) and the attribute's value is not returned in an ldapsearch for the account unless the attribute is explicitly requested in the search.

Environment

IM 12.6.8 ConnectorXpress managing Oracle Unified Directory (OUD)

Resolution

In ConnectorXpress when defining the attribute mappings for the project, since the operational attributeĀ ds-pwp-account-disabled will not appear in the drop-down list of available attributes you can explicitly type the attribute name.