]
Alessio Soldano commented on WFLY-3987:
---------------------------------------
Marcus,
I'm getting back to this after some time. I think the best you could do is provide a
reproducer or at least a proper wsdl file that I can try building a contract first
endpoint and a client for.
The fact you're seeing different behavior running in and out of container is possibly
because you're using the RI (JDK) JAXWS implementation out of container.
Regression regarding WS Client when using header authentication
---------------------------------------------------------------
Key: WFLY-3987
URL:
https://issues.jboss.org/browse/WFLY-3987
Project: WildFly
Issue Type: Bug
Components: Web Services
Affects Versions: 8.1.0.Final, 9.0.0.Alpha1
Environment: Linux (Ubuntu 14.04), OpenJDK 1.7.0_65, Wildfly 8.0/8.1/9.0A
Reporter: Marcus Carlson
Assignee: Alessio Soldano
I'm trying to integrate a Web Service client based on BMC Remedy product where Web
service authentication is handled in Soap Header and not basic authentication. See
AuthenticationInfo element on
https://github.com/macmorning/itsm_mobileview/blob/master/SoapUI%20Projec...
for an example of how the WSDL file looks like.
I've enabled Xadditionalheaders so I get the AuthenticationInfo as the last argument,
like this:
{noformat}
port.helpDeskQueryListService(qualification, startRecord, maxLimit, authInfo);
{noformat}
Problem is that this was working fine in WildFly 8.0 generating the following SOAP
Request:
{noformat}
ID: 1
Address:
https://SERVER/arsys/services/ARService?server=SERVER&webService=HPD_...
Encoding: UTF-8
Http-Method: POST
Content-Type: text/xml
Headers: {Accept=[*/*],
SOAPAction=["urn:HPD_IncidentInterface_WS/HelpDesk_QueryList_Service"]}
Payload: <soap:Envelope
xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"><s...
xmlns="urn:HPD_IncidentInterface_WS"><userName>SECRETUSER</userName><password>SECRETPASSWORD</password></AuthenticationInfo></soap:Header><soap:Body><HelpDesk_QueryList_Service
xmlns="urn:HPD_IncidentInterface_WS"><Qualification>'Status' =
"Closed"</Qualification><startRecord>0</startRecord><maxLimit>1000</maxLimit></HelpDesk_QueryList_Service></soap:Body></soap:Envelope>
{noformat}
With 8.1 it's generating a completly different payload with the Header element in
Body and body completly missing (!):
{noformat}
ID: 2
Address:
https://SERVER/arsys/services/ARService?server=SERVER&webService=HPD_...
Encoding: UTF-8
Http-Method: POST
Content-Type: text/xml
Headers: {Accept=[*/*],
SOAPAction=["urn:HPD_IncidentInterface_WS/HelpDesk_QueryList_Service"]}
Payload: <soap:Envelope
xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"><s...
xmlns="urn:HPD_IncidentInterface_WS"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:type="AuthenticationInfo"><userName>SECRETUSER</userName><password>SECRETPASSWORD</password></HelpDesk_QueryList_Service></soap:Body></soap:Envelope>
{noformat}
I've also tried 9.0.0.Alpha1 with same result. What could be wrong?