Workflow REST Web Service node returns "RSA002 : Invalid Configuration" message in RSA Identity Governance & Lifecycle
Originally Published: 2019-09-27
Article Number
Applies To
RSA Version/Condition: 7.0.2, 7.1.0, 7.1.1
Issue
PublicData_HttpStatusCode 200
PublicData_HttpStatusMsg OK
PublicData_StatusCode RSA002 : Invalid Configuration
PublicData_HttpStatusMsg OK
PublicData_StatusCode RSA002 : Invalid Configuration
The aveksaserver.log will not show the same message, however, if debug is enabled, you may see the following error message in the aveksaServer.log :
Error while converting the response into xml in parserPremature end of file.
Please refer to RSA Knowledge Base Article 000030317 -- Artifacts to gather in RSA Identity Governance & Lifecycle to find the location of the log files for your specific deployment.
Cause
Resolution
- RSA Identity Governance & Lifecycle 7.0.2 P15
- RSA Identity Governance & Lifecycle 7.1.0 P08
- RSA Identity Governance & Lifecycle 7.1.1 P03
- RSA Identity Governance & Lifecycle 7.2
Workaround
Notes
Related Articles
FSM error: ADAP-10045 : Invalid argument 3Number of Views FSGUI-34203 : Host already configured 1Number of Views In Rest Web Service Node, the Response Variables does not appear to accept Integer or Boolean values in RSA Governance & L… 67Number of Views SecurID prompt does not appear using Chrome and Firefox after adding a Security Policy on RSA Agent 8.0.3 for Apache web s… 34Number of Views Source variable and target variable are showing duplicate values when adding a new value on Next Value node in RSA Via Lif… 38Number of Views
Trending Articles
Download RSA SecurID Access Cloud User Event audit logs using Cloud Administration REST API CLU RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory Authentication Manager Security Console and Operations Console Inaccessible After Certificate Update Authentication Manager How to Retrieve the LDAPS Certificate and Configure an External Identity Source to Use LDAPS
Don't see what you're looking for?