LDAP Error 17 after extending schema
search cancel

LDAP Error 17 after extending schema

book

Article ID: 41658

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

Issue:  

After extending the Active Directory Schema and adding custom attributes you may receive an error code 17 when launching a task in Identity Manager.

Environment:  

12.5 & 12.6

Cause: 

If you have created a new attribute on your user directory, your Identity Manager environment usually recognizes it. In rare cases it does not, you will want to make sure you take the following steps.

Workaround:

1.       Make sure these steps were followed thoroughly:

a.       https://docops.ca.com/ca-imag-connectors/1-0/EN/microsoft-active-directory-microsoft-exchange-and-microsoft-lync/configure-the-connection-to-active-directory/extend-the-active-directory-schema-by-adding-custom-attributes

2.       Make sure your attributes are mapped properly in provisioning manager.

3.       Make sure the user has proper permissions to add that custom attribute. 

4.       The directory schema may not have been updated on the corporate store router that is located on Application server. 

Environment

Release:
Component: IDMGR