WSS4J bug prevents SAML token to be validated

Solution Verified - Updated -

Issue

  • While using wss4j to validate saml token inside soap messages. After upgrading from version 2.2.7.redhat-00001 to 2.4.1.redhat-00005 during camel 3 upgrade to version 3.18.3.redhat-00022 to version 3.20.1.redhat-00026, - experienced a newly introduced error when validating a saml 1.0 assertion in our camel route.

Environment

  • Camel for Spring Boot
    • 3.20.0

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