SOAP Web Service AFX test connector capabilities fail with 'Failed to create service' and 'Unexpected EOF in prolog' messages in RSA Identity Governance & Lifecycle

[#1]

Article Number

000034248

Applies To

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

Issue

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

Failed to create service
 

Looking at the file with a name similar to $AFX_HOME/esb/logs/esb.AFX_CONN_{connector-name}_test.log, you first see:
 

2019-09-27 07:59:22.091 [INFO] com.aveksa.AFX.server.runtime.mule.soap.mule.SoapDispatchComponent:197 - Issue encountered supported verb: CreateAccount, error is org.apache.cxf.service.factory.ServiceConstructionException: Failed to create service. 2019-09-27 07:59:22.093 [ERROR] com.aveksa.AFX.server.runtime.mule.soap.mule.SoapDispatchComponent:365 - Error occured while executing the capability javax.xml.ws.WebServiceException: org.apache.cxf.service.factory.ServiceConstructionException: Failed to create service. at org.apache.cxf.jaxws.ServiceImpl.<init>

 

Note in versions prior to RSA Identity Governance & Lifecycle v7, the AFX log file name would be similar to $AFX_HOME/mulelogs/mule.AFX_CONN_{connector-name}_test.log.

Further down the stack trace is the message:

 

Caused by: javax.wsdl.WSDLException: WSDLException: faultCode=PARSER_ERROR: com.ctc.wstx.exc.WstxEOFException: Unexpected EOF in prolog at [row,col,system-id]: [1,0,"http://xxxxxxxx:9080/WebSecurityWebService/services/WebSecurity?WSDL"]

The WSDL file being referenced works as expected when accessed from the SoapUI.

Cause

The significant error message here is the last error message:
 

Unexpected EOF in prolog

This error indicates that there is a parsing issue in the WSDL file being accessed.

When pulling up the WSDL file in Notepad++ or a similar editor, you can see that the lines are terminated by CRLF. This indicates that the WSDL file might have been created on Windows, and the Linux Operating System does not necessarily interpret this character correctly. SoapUI tends to be more forgiving and has no issue with the CRLF character.

Resolution

The solution involves two steps:

1. Edit the WSDL file and remove the CRLF characters at the end of the lines. An example is provided below:

Image description

2. Convert the file to Unix format. For example, if you are using Notepad++, select Edit > EOL Conversion > UNIX/OSX Format. 

Image description

3. Save the file using File > Save.