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.