Thanks for your patience Colm.
I began asserting the TRANSPORT_TOKEN in my interceptor as I got the
following message in the logs, on both the client and server-side:
An exception was thrown when verifying that the effective policy for this
request was satisfied. However, this exception will not result in a fault.
The exception raised is: org.apache.cxf.ws.policy.PolicyException: These
policy alternatives can not be satisfied:
{http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702}TransportToken
I can't see where this policy is asserted anywhere in the
TransportBindingHandler/TransportBinding/TransportToken. Can that warning be
ignored?
Finally, the neethi Assertion#serialize method. It is never called for my
Token subclass. I almost feel like it would be called to get the xml
representation of an effective policy from a 'top-level' Policy object like
TransportBinding. Can you tell me under what circumstances it is called?
Thanks
Dirk
--
View this message in context:
http://cxf.547215.n5.nabble.com/Custom-SecurityPolicy-Assertions-and-the-Symmetric-binding-tp5754879p5755233.html
Sent from the cxf-user mailing list archive at Nabble.com.
