Hello all,
I'm working with OSB 12c, and I'm trying with OWSM with a simple username token policy (oracle/wss_username_token_service_policy) over a simple 'Echo' Service.
The test are executed from SOAPUI.
Without OWSM Policy attached, the result of the test are righ, so when I attach the policy to the proxy, the error is like that:
soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope">
<soap:Body>
<soap:Fault>
<soap:Code>
<soap:Value>soap:Receiver</soap:Value>
</soap:Code>
<soap:Reason>
<soap:Text xml:lang="en">OSB-382000: Unsupported Content-Type: application/soap+xml;charset=UTF-8;action="echo" Supported ones are: [text/xml]</soap:Text>
</soap:Reason>
<soap:Detail>
<con:stack-trace xmlns:con="http://www.bea.com/wli/sb/context">com.bea.wli.sb.service.handlerchain.HandlerException: Unsupported Content-Type: application/soap+xml;charset=UTF-8;action="echo" Supported ones are: [text/xml]
at com.bea.wli.sb.service.disi.handlerchain.handlers.InboundDISIHandler.dispatch(InboundDISIHandler.java:148)
at com.bea.wli.sb.service.handlerchain.handlers.AbstractHandler.dispatch(AbstractHandler.java:131)
......
The only difference between the envelopes is the header when I call to the proxy with security:
<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope" ...
<soap:Header>
<wsse:Security soapenv:mustUnderstand="1" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
<wsse:UsernameToken wsu:Id="UsernameToken-4" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
<wsse:Username>weblogic</wsse:Username>
<wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">12345678</wsse:Password>
</wsse:UsernameToken>
</wsse:Security>
<soap:Header>
....
Finally, another interesting antecedent is if I deploy the same service in OSB 11g and add the same owsm policy, the response is righ.
Can anyone help me with this issue?
Thanks!