[jboss-jira] [JBoss JIRA] (WFLY-3987) Regression regarding WS Client when using header authentication

[Marcus Carlson (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-3987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13020581#comment-13020581 ] 

Marcus Carlson commented on WFLY-3987:
--------------------------------------

Hm. Not sure everything is well anyway. I've been trying for the last couple of days to get HelpDesk_Query_Service method working but with no luck. Both HelpDesk_QueryList_Service and HelpDesk_GetWorkInfoList seems to be working just fine with the workaround.

The only difference I can find is that HelpDesk_Query_Service is translated into a void method with output parameters and the other some kind of list object.

Testing this outside of Wildfly with just a simple main method and manually creating the HPDIncidentInterfaceWSService field to a new instance and run it's working every time. Not sure what implementations are used then - maybe standard Java / Sun (?) libraries.

So, something is not working that well although I'm workaround this by not using the methods at all at the moment...

Let me know if there's anything you need to know or something I should test.

> 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%20Projects/HPD-IncidentInterface-WS---v8-soapui-project.xml 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_IncidentInterface_WS
> 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/"><soap:Header><AuthenticationInfo 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_IncidentInterface_WS
> 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/"><soap:Body><HelpDesk_QueryList_Service 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?



--
This message was sent by Atlassian JIRA
(v6.3.8#6338)