I was trying to apply the oracle Predefined auth.xml WS-policy to the osb proxy service and that will query a web service that is running on separate weblogic server, but I'm getting MustUnderstand SOAP fault does anyone seen this fault in OSB. Do I have to do any configuration changes on WLS?
Proxy configured with:
General tab -> WSDL based proxy service, this wsdl doesn't have ws-policy definitions inside.
Transport tab -> Get all headers = no
HTTP Transport tab -> HTTPS Required = No / Authentication = Basic
Operation tab -> Enforce WS-I Compliance = not checked / Selection Algorithm = SOAP Body Type
Message Content tab -> default settings
Policy -> Added Auth.xml(predefined) policy to request policies.
Security tab -> Process WS-Security header = No / Custom Authentication settings = none
I'm using the following SOAP Message .
when I change the mustunderstand="false" then it goes through.
Thanks for that it worked when I use the OSB test console. I'm getting the error message when I type in the wrong user, now I'm going to use a Soapui as client to test it. and will let you know how I go
I was able to use the soapui as a client to test the Auth.xml, but if I type in the wrong username or password I'm only getting the requested payload back on the soapui response. if I wanted to send the meaningful error message to the client like *"Authentication Failed"* how do I do this in the OSB Proxy service? I tried error handler but no luck, Can anyone point me in the write direction?
I removed the reply with failure action from service error handler and it worked. I could see the SOAP fault message in soapui as shown below, but I don't understand why reply with failure didn't work.