When editing/creating a SOAP Web Service AFX Connector and configuring any capability, a 'Request could not be handled' message is thrown in RSA Identity Governance & Lifecycle
2 years ago
Originally Published: 2016-09-14
Article Number
000043408
Applies To
RSA Product Set: Identity Governance & Lifecycle 
RSA Version/Condition: 6.9.0, 6.9.1
Issue
When editing/creating a SOAP Web Service AFX Connector in RSA Identity Governance & Lifecycle (AFX > Connectors > {connector-name} > Edit > Capabilities tab) and configuring any connector capability, the following error occurs in the user interface:
 
The request could not be handled.
 
User-added image
Cause
This issue has been reported in engineering ticket ACM-51465.

This issue is due to incorrect or invalid configurations on the Settings tab. There are multiple different ways to produce this error.  Some examples are:
  • NoAuth/Basic Auth Connector creation with Incorrect WSDL URL
  • NoAuth Connector creation with BASIC AUTH WSDL Url provided with credentials
  • BASIC AUTH SOAP Connector with Invalid Credentials
  • BASIC AUTH SOAP Connector with No Credentials
Additional details that may help troubleshooting the WSDL connection can be found in the aveksaServer.log.

Please refer to RSA Knowledge Base Article 000030327 -- Artifacts to gather in RSA Identity Governance & Lifecycle to find the location of the aveksaServer.log for your specific deployment.
 
Resolution
This issue is resolved in RSA Identity Governance & Lifecycle 7.0.0 and above.

In version 7.0 RSA Identity Governance & Lifecycle has implemented more robust error handling in this area to provide better feedback as to what exactly is wrong with the WSDL information that is provided.

Related Articles

Trending Articles

Don't see what you're looking for?