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
Cloud Authentication Service Integration 10Number of Views An unexpected JavaScript error ('remoteCAs[...].catype' is null or not an object) has occurred in RSA Registration Manager 59Number of Views LDAP exception occurred getting attributes for the class <Object Class name> from LDAP server when testing connection to i… 142Number of Views FileCloud-SecurID-Access-SAML-Integration 11Number of Views A newly configured RSA SecurID Access Identity Router is in Inactive state in the Administration Console 173Number of Views
Don't see what you're looking for?