OSB message level authentication fault and predicate

Question

Hi,
I have successfully configured MLS on my proxy service and it works fine.
However, the fault thrown back by OSB does not give you much when authorization fails.
Is it possible to get the predicate that has not been fulfilled? It would be more useful to the consumer of the service.
Also, is it possible to at least trace/log the predicate on authorization failure?
The logs contain the operation that failed but not the predicate
\[OSB Security:386004\] Message-level access control denied access to proxy service Main/Proxy Service/LocalFundPS, operation findAllSchemes, subject: XXX
Thanks
Arnaud
<faultcode>soapenv:Server</faultcode>
<faultstring>
BEA-386102: Message-level authorization denied
</faultstring>
<detail>
<con:fault xmlns:con="http://www.bea.com/wli/sb/context">
<con:errorCode>BEA-386102</con:errorCode>
<con:reason>Message-level authorization denied</con:reason>
<con:location>
<con:path>request-pipeline</con:path>
</con:location>
</con:fault>
</detail>
</soapenv:Fault>

Answer 1

I have authentication providers configured as below (in the same order)
Custom authenticatio provider - REQUIRED
DefaultAutentication Provider - OPTIONAL
I did configured message level authentication in proxy service for custom username/password token.
Craeted a new user in weblogic console.
Invoked proxy service with newly created username/password.
I expect the user should not be authenticated since authetication with custom authentication provider will fail, which is required.
I'm getting user authenticated and business service invoked and got a valid response.
If i open another browser window and try to login with the weblogic admin password, it does not let me in because the user is not authenticated by my custom provider.
Hope this makes scenario clear.