Symantec IGA

Expand all | Collapse all

SOAP call from Policy Xpress

Jump to Best Answer
  • 1.  SOAP call from Policy Xpress

    Posted 07-24-2018 05:16 AM

    Hi guys,

     

    I'm trying to create a PX to send a SOAP call to a webservice. I developed the webservice myself, and tests via SOAPui/POSTman all give me the required result. Only when I try to create the PX I get the following error:

     

    The test has failed to run with following error: "Failed running web service " which was caused by "Could not send Message.;HTTP response '401: Unauthorized' when communicating with http://<HOSTNAME>?SingleWSDL".

    and the server.log states the following:

     WARN [ims.policyxpress.PxActionExecuteSOAPQuery] (Thread-145 (HornetQ-client-global-threads-267255905)) Gathering wsdlURL http://<HOSTNAME>/PsServiceLibrary?SingleWSDL
    WARN [ims.policyxpress.PxActionExecuteSOAPQuery] (Thread-145 (HornetQ-client-global-threads-267255905)) Gathering username
    WARN [ims.policyxpress.PxActionExecuteSOAPQuery] (Thread-145 (HornetQ-client-global-threads-267255905)) Gathering password
    WARN [ims.policyxpress.PxActionExecuteSOAPQuery] (Thread-145 (HornetQ-client-global-threads-267255905)) Gathering operation http://Microsoft.ServiceModel.Samples/IPsService/UserAccountActions
    WARN [ims.policyxpress.PxActionExecuteSOAPQuery] (Thread-145 (HornetQ-client-global-threads-267255905)) Gathering soapVersion 1.1
    WARN [ims.policyxpress.PxActionExecuteSOAPQuery] (Thread-145 (HornetQ-client-global-threads-267255905)) Gathering soapRequestBody <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:mic="http://Microsoft.ServiceModel.Samples" xmlns:wsdl="http://tews6/wsdl">
    <soapenv:Header/>
    <soapenv:Body>
    <wsdl:TaskContext>
    <wsdl:admin_id><USERNAME></wsdl:admin_id>
    <wsdl:admin_password><PASSWORD</wsdl:admin_password>
    </wsdl:TaskContext>
    <mic:UserAccountActions>
    <mic:strTargetUser><client data></mic:strTargetUser>
    <mic:strActionUser><client data></mic:strActionUser>
    <mic:strCaId>123</mic:strCaId>
    <mic:strFunction>A</mic:strFunction>
    </mic:UserAccountActions>
    </soapenv:Body>
    </soapenv:Envelope>
    WARN [ims.policyxpress.PxActionExecuteSOAPQuery] (Thread-145 (HornetQ-client-global-threads-267255905)) Gathering namespace
    WARN [ims.policyxpress.PxActionExecuteSOAPQuery] (Thread-145 (HornetQ-client-global-threads-267255905)) Gathering service_name
    WARN [ims.policyxpress.PxActionExecuteSOAPQuery] (Thread-145 (HornetQ-client-global-threads-267255905)) Gathering port_type
    WARN [ims.policyxpress.PxActionExecuteSOAPQuery] (Thread-145 (HornetQ-client-global-threads-267255905)) Gathering service_method Message
    WARNING [org.apache.cxf.phase.PhaseInterceptorChain] (Thread-202 (HornetQ-client-global-threads-267255905)) Interceptor for #{http://cxf.apache.org/jaxws/dispatch}Invoke has thrown exception, unwinding now: org.apache.cxf.interceptor.Fault: Could not send Message.
    at org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSenderInterceptor.java:64)
    at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:272)
    at org.apache.cxf.endpoint.ClientImpl.doInvoke(ClientImpl.java:570)
    at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:479)
    at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:382)
    at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:335)
    at org.apache.cxf.endpoint.ClientImpl.invokeWrapped(ClientImpl.java:370)
    <VERY LONG STACKTRACE>
    Caused by: org.apache.cxf.transport.http.HTTPException: HTTP response '401: Unauthorized' when communicating with http://<HOSTNAME>?SingleWSDL

    If anyone has any thoughts, I would be happy to hear them.



  • 2.  Re: SOAP call from Policy Xpress
    Best Answer

    Broadcom Employee
    Posted 07-25-2018 02:30 AM

    Also tracked via a Support case. We are looking for some additional, onsite experience to be shared for a similar attempt.

    Currently checking whether this is related to the actual password used to connect to the web service and the way it passed from IM.

     

    Rinat

    CA Tech Support