SOAP Web Service AFX test connector capabilities fail with 'Could not find service named' in RSA Identity Governance & Lifecycle

RSA Product Set: Identity Governance & Lifecycle 
RSA Version/Condition: 6.9.1, 7.0.x
 

When testing SOAP Web Service AFX connector capabilities (AFX > Connectors > {connector-name} > Test Connector Capabilities) the following error message displays in the user interface:

Could not find service named
 

This error is reported in the connector log file, $AFX_HOME/esb/logs/esb.AFX_CONN_{connector-name}_test.log (7.x) or $AFX_HOME/mule/logs/mule.AFX_CONN_{connector-name}_test.log (6.x):

2019-12-21 14:27:04.067 [INFO] com.aveksa.AFX.server.runtime.mule.soap.mule.SoapDispatchComponent:197 - Issue encountered supported verb: CreateAccount, error is Could not find service named {http://schemas.microsoft.com/clr/nsassem/RemoteProgramExits/RemoteProgramExits20Version2C3Dneutral20PublicKeyToken%3Dnull}RemoteProgramExitsService in wsdl http://test.testla.testfrd.xyz.com:XXXX/RemoteProgramExits.soap?WSDL
2019-12-21 14:27:04.069 [INFO] org.mule.api.processor.LoggerMessageProcessor:197 - Error on SOAP component handling, no post processing done

This error will occur if the WSDL namespace contains special characters such as a percent (%) sign or a space. In this case the SOAP Web Service AFX connector does not parse the namespace URL properly.

EXAMPLE:

In the below WSDL note the actual target namespace is:
   
In the log file note the parsed target namespace is:
   

This issue is resolved in the following RSA Identity Governance & Lifecycle patches:

• RSA Identity Governance & Lifecycle 6.9.1 P12
• RSA Identity Governance & Lifecycle 7.0.1 
• RSA Identity Governance & Lifecycle 7.0.2

1. Login to the afx server as the afx user.
2. cd $AFX_HOME/esb/apps/{connector-name} (7.x) or $AFX_HOME/mule/apps/{connector-name} (6.x)
3. vi connector-flow.xml 
4. Locate the namespace seen in the error and replace the incorrectly parsed (truncated) namespace with the actual namespace defined in the WSDL definition. In this example,

5. Save the file after making changes.
6. vi mule-config.xml
7. Locate </mule> and add a new blank line after </mule>.
8. Save the file. This performs a hot deployment of the connector.
9. Check that the connector is in a Running state. In the user interface go to AFX > Connectors.
10. If the connector is in a Running state, test the connector capability to verify the workaround.