How to ignore an unwanted UsernameToken in JBossWS-CXF in EAP 6

Solution Unverified - Updated -


We are migrating an application to JBoss EAP 6. The previous client was using UsernameToken, but that is no longer necessary. Therefore UsernameToken is not defined in the WSDL policy of the endpoint. Nonetheless, the client is still sending the UsernameToken to the endpoint, causing an authentication error.

Is there a way that CXF can just ignore the incoming UsernameToken SOAP header?

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content