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

Solution Unverified - Updated -

Issue

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 of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.