Administration Guide › CA Role & Compliance Manager Integration › How to Configure Integration with CA RCM › How to Configure a Connection in CA RCM › Select Endpoints and Resources › Connector for Identity Manager Limitations with Active Directory

Connector for Identity Manager Limitations with Active Directory

The following issues apply to using the connector for Active Directory:

• CA RCM account template handling must be based on an AD account policy or an AD contact policy.

  The connector can poll and update only one of these policy types.

• Account templates should reference only one endpoint.
• During data export, the connector does not accurately parse some change entries in the audit card.
• When you configure the connector, you must assign a DN field for each data type that is exported.
• The connector may generate non-standard CSV files during data retrieval. To correct this situation, edit the endpoint mapping xml file:
  1. On the computer that hosts the CA RCM client tools, browse to the directory:

     RCM_install\Client Tools\Software\Converters\CA\conf
     

     Note: RCM_install is the CA RCM installation directory.

  2. Edit the endpointTypeMapping.xml file, as follows:
     1. Under the Active Directory endpoint type, find the resource element named Active Directory Group.
     2. Change the values of the constant-link and replace-in-links elements as shown in the following example.

Example: EndpointTypeMapping.xml Updated for Active Directory Connector

The following example shows you how to update the endpoint mapping file to prevent the Active Directory connector generating non-standard CSV files during data retrieval:

<resource description="Active Directory Group"

resource-class="eTADSGroup"
resource-name-attribute="eTADSGroupName"
resource-referenced-attribute="eTADSdistinguishedName"
resource-appears-in-attribute="eTADSmemberOf"
friendly-name-transformation="FIRST_DN_PART"
ignore-problematic-resources="true">
<constant-link
value="CN=Cert Publishers,CN=Users,DC=eurekify,DC=corp"/>
<replace-in-links 
pattern="DC=\?"
new-value="DC=eurekify,DC=corp"/>

</resource>