I encountered the same problem as described in this post: http://old.nabble.com/An-invalid-security-token-was-provided-%28Bad-UsernameToken-Values%29-ts27429163.html#a27429163 An invalid security token was provided (Bad UsernameToken Values)
In the thread posts Daniel Kulp mentions configuring the WSSConfig object, but said also that that was not yet available in a release. The code line below should do the trick according to Daniel: WSSConfig.getDefaultWSConfig().setAllowNamespaceQualifiedPasswordTypes(true); User huidong at the end of the thread mentions modifying the spring configuration file, by specifying arguments to the WSS4JInInterceptor constructor and modifying the WSS4JInInterceptor class. My questions: Which is the best/prefered approach? Can you provide an example of how to go about modifying the WSS4JInInterceptor, if that is what's required? -- View this message in context: http://old.nabble.com/Bad-UsernameToken-Values-due-to-.NET-compliance-problem---how-to-solve--tp28524226p28524226.html Sent from the cxf-user mailing list archive at Nabble.com.
