Path resolution SOAP

[Anon Anon]

Hi CA Community,

 

I created a SOAP Web Service on a gateway in DMZ with "Publish SOAP Web Service" and I added a WSDL from a file.

For the resolution path, I selected "Custom resolution path" and I just write /test.

 

When I try to access the service with Postman, I obtain this error :

 

<?xml version="1.0" encoding="UTF-8"?>

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">

    <soapenv:Body>

        <soapenv:Fault>

            <faultcode>soapenv:Server</faultcode>

            <faultstring>Policy Falsified</faultstring>

            <faultactor>https://<ip_adress>/test</faultactor>

            <detail>

                <l7:policyResult

                    status="Service Not Found.  The request may have been sent to an invalid URL, or intended for an unsupported operation." xmlns:l7="http://www.layer7tech.com/ws/policy/fault"/>    

            </detail>   

        </soapenv:Fault>

    </soapenv:Body>

</soapenv:Envelope>

 

Is there an explanation to this kind of behaviour ? Do I have to had headers for my request ?

I can't also find logs to see what happens.

 

Thank you for your help !

[Doyle_Reece]

Hey Chovine,

 

     Since this is a web service ( associated with a wsdl ), i'd highly recommend using a tool like SoapUI to test these out. In soapUI when you prepare your request, it'll ask for the wsdl, with this, it will build out your sample requests... more than likely you're missing the operation/SoapAction that is required for 'Resolution', in which SoapUI makes it a lot easier to test these things out. Once you get a good understanding of what is expected to be sent, you can then try to mimic that in PostMan, which doesn't baby you as much as SoapUI does .

 

hope this helps,

 

Doyle