Generic REST AFX Connector fails with ValidationError in RSA Identity Governance & Lifecycle
Originally Published: 2020-08-13
Last Modified: 2023-11-30
Article Number
Applies To
RSA Version/Condition: 7.0.x, 7.1.0, 7.1.1, 7.2.0
Issue
Error code = 4
ValidationError
Cause:
{"code":"InvalidData",...
ValidationError
Cause:
{"code":"InvalidData",...
Input parameters are defined under AFX > Connectors > {Connector name} > Edit > Capabilities tab > {Capability name}.
Cause
Resolution
For example, if the Request Header Content-Type is set to:
application/jsonChange the Request Header Content-Type to:
application/json;charset=UTF-8
EXAMPLE:
Related Articles
Generic REST AFX Connector does not encrypt Additional Parameters when defined as Encrypted in RSA Identity Governance & L… 105Number of Views RSA ID Plus Admin Logs Connector - RSA Ready Implementation Guide 23Number of Views RSA Governance & Lifecycle SaaS - Deploying the Remote Collection Agent 49Number of Views Zoho Directory - SAML My Page SSO Configuration - RSA Ready Implementation Guide 7Number of Views Generic REST Collector fails with 'com.aveksa.client.genericrest.GenericRestException: UNEVEN_JSON_PATH_CONFIGURATION' in … 280Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device Manual synchronization introduced in RSA Authentication Manager 8.2 Service Pack 1 patch 6 Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory How to verify NTP server synchronization is not working in RSA Authentication Manager 8.x RSA Governance & Lifecycle 8.0.0 Installation Guide
Don't see what you're looking for?