[CXF-7536] STRTransform TransformException when manually adding SAML Assertion via SAMLCallback.setAssertionElement()

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.1.14, 3.2.1
• Labels: security

Environment

Apache Tomcat 8.0.37

• Estimated Complexity: Unknown
• Assignee: Colm O hEigeartaigh
• Reporter: Russell Orf
• Created: 17/Oct/17 16:48
• Updated: 28/Nov/17 10:51
• Resolved: 23/Oct/17 14:50

Description

In Apache CXF v3.1.7, I have a JAX-WS web service client calling a service that requires a HolderOfKey SAML Assertion. The assertions are from a custom service that does not adhere to the WS-Trust SecureTokenService standard, so I am adding them manually in a SAMLCallbackHander, using the callback.setAssertionElement() method.

When invoking the client, the WSS4J framework is unable to compute the signature for the SecurityTokenReference header block, throwing the below error:

{{
javax.xml.crypto.dsig.XMLSignatureException: javax.xml.crypto.dsig.TransformException: org.apache.wss4j.common.ext.WSSecurityException: Referenced token "id-of-SAML-assertion" not found
at org.apache.wss4j.dom.str.STRParserUtil.getTokenElement(StrParserUtil.java:314)
at org.apache.wss4j.dom.transform.STRTransformUtil.dereferenceSTR(STRTransformUtil.java:98)
at org.apache.wss4j.dom.transform.STRTransform.transformIt(STRTransform.java:195)}}

It appears that the SAML assertion DOM Element that is added via the callback.setAssertionElement() method is not getting searched by the STRParserUtil.getTokenElement() method.