Import of an AFX connector does not show the display name of the connector in RSA Identity Governance & Lifecycle
Originally Published: 2020-01-31
Article Number
Applies To
RSA Version/Condition: 7.1.1, 7.2.0
Issue
In the following example, an AFX connector named Dog-Prod_1 is exported. When the connector package is imported into another system, the only name available for import is Dog-Conn_1.
- The below AFX connector named Dog-Prod_1 is exported.
- When importing the Dog-Prod_1 AFX connector, the import says Dog-Conn_1. There is no other column name that can be displayed under Table Options > Columns tab.
- A review of the XML file that contains the connector definition, shows the <name> of the connector as Dog-Conn_1 and the <displayName> as Dog-Prod_1.
Cause
If you edit an AFX connector and change the name, it is actually only the display name that gets changed. The original name cannot be changed because it is the unique identifier for the connector. The problem is that when you import the connector, it shows the unique name rather than the display name. In the example, the AFX connector name has been changed from Dog_Conn_1 to Dog-Prod_1.
This is a known issue reported in engineering ticket ACM-103127.
Resolution
Workaround
For example,
- In Windows extract the connector package. This will create a directory with the same name as the package.
- Go the connector package directory just created.
- Go to acmExportConnector > connector > CONNECTOR.
- Edit Connector.xml.
- Under the <connector> section note the <name> and <displayName> of the connector.
- <displayName> is the name as you know it listed under AFX > Connectors. In this example: Dog-Prod_1.
- <name> is the name of the connector as shown during the connector import. In this example: Dog-Conn_1.
- Import the connector again using the <name> of the connector: Dog-Conn_1.
Related Articles
Unification and collectors get stuck at calculating role metrics after applying P01 to Via L&G v7.0.0 13Number of Views All change requests are stalled or in open state in RSA Identity Governance and Lifecycle 54Number of Views Applying role changes in RSA Identity Governance & Lifecycle takes longer to complete when Generate Indirect Entitlements … 37Number of Views FIM 4.x - What JAVA JDK Should be Used with WebLogic 9 or WebLogic 10 with FIM 4.x 16Number of Views Workflows stuck in AFX fulfillment and/or Provisioning nodes in RSA Identity Governance & Lifecycle 526Number of Views
Trending Articles
RSA Authentication Manager 8.9 Setup and Configuration Guide How to 'Trust' the RSA Authentication Manager Security Console Self-Signed Root CA certificate and prevent Cert warnings. RSA Authentication Manager 8.9 Release Notes (January 2026) Configure RSA Authentication Manager as a Secure Proxy Server for Cloud Access Service RSA Authentication Manager Upgrade Process
Don't see what you're looking for?