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
Last Modified: 2023-11-30
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
FileCloud-SecurID-Access-SAML-Integration Number of Views Cloud Authentication Service Integration Number of Views An unexpected JavaScript error ('remoteCAs[...].catype' is null or not an object) has occurred in RSA Registration Manager 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 HTTP Federation Proxy Applications Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device Reporting on RSA Authentication Manager 8.x users with On-Demand Token, a fixed passcode or a hardware/software token assi… How to Download OTP Token Seed Files from myRSA Anomalix idGenius - SAML Relying Party Configuration - RSA Ready Implementation Guide RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide
Don't see what you're looking for?
