Access Fulfillment Express (AFX) Connector import fails to import enabled capabilities if no mappings are defined in RSA Identity Governance & Lifecycle
Originally Published: 2018-10-19
Article Number
Applies To
RSA Version/Condition: 7.0.x
Issue
Cause
When using AFX, the capabilities require mappings. The exception to this is when using a provisioning node in a fulfillment workflow. When using a provisioning node, the AFX capabilities need to be enabled but no mappings are required.
This is a known defect reported in engineering ticket ACM-76107 as the import of connectors did not consider this use case.
Resolution
Workaround
Related Articles
An unexpected JavaScript error ('remoteCAs[...].catype' is null or not an object) has occurred in RSA Registration Manager Number of Views Cloud Authentication Service Integration Number of Views LDAP exception occurred getting attributes for the class <Object Class name> from LDAP server when testing connection to i… Number of Views Enable RSA Authenticator App Users to Access Resources Protected by RSA Authentication Manager 8.4 Patch 3 and Earlier Number of Views FileCloud-SecurID-Access-SAML-Integration Number of Views
Trending Articles
RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide RSA Release Notes for RSA Authentication Manager 8.8 Troubleshooting RSA MFA Agent for Microsoft Windows How to download and install the AFX Server Archive in RSA Identity Governance & Lifecycle The Template ({Connector Template Name}) has missing file content error when creating AFX Connectors in RSA Identity Gover…
Don't see what you're looking for?
