Yeah, take a look at the "assertTokens" method here: https://git-wip-us.apache.org/repos/asf?p=cxf.git;a=blob_plain;f=rt/ws/security/src/main/java/org/apache/cxf/ws/security/wss4j/UsernameTokenInterceptor.java;hb=HEAD
Obviously you only want to assert the policies if the correct type of UsernameToken was received, etc. Colm. On Thu, Oct 30, 2014 at 5:21 PM, SRog <[email protected]> wrote: > Hey there, > now I got the following fault: > > <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/";> > <soap:Body> > <soap:Fault> > <faultcode>soap:Server</faultcode> > <faultstring>These policy alternatives can not be satisfied: > { > http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702}SupportingTokens > {http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702}UsernameToken > </faultstring> > </soap:Fault> > </soap:Body> > </soap:Envelope> > > This is what you meant when talking about policy validation stage will > fail? > > When I take a look at DefaultCryptoCoverageChecker I do not see the right > place where I could add the assertion. Is there an example how I could do > this? > > Thanks, > SRog > > > > > -- > View this message in context: > http://cxf.547215.n5.nabble.com/Username-PWD-on-STS-tp5750076p5750471.html > Sent from the cxf-user mailing list archive at Nabble.com. > -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com
