Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id AC2A9200D20 for ; Tue, 17 Oct 2017 18:56:07 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id AA5BB1609EB; Tue, 17 Oct 2017 16:56:07 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id BF4541609D9 for ; Tue, 17 Oct 2017 18:56:06 +0200 (CEST) Received: (qmail 57216 invoked by uid 500); 17 Oct 2017 16:56:05 -0000 Mailing-List: contact dev-help@ws.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ws.apache.org Delivered-To: mailing list dev@ws.apache.org Received: (qmail 57206 invoked by uid 99); 17 Oct 2017 16:56:05 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 17 Oct 2017 16:56:05 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 8EEC518073A for ; Tue, 17 Oct 2017 16:56:04 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id lyrw5_NzdhUV for ; Tue, 17 Oct 2017 16:56:03 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id BC1B160F1A for ; Tue, 17 Oct 2017 16:56:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id E2620E0F3B for ; Tue, 17 Oct 2017 16:56:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 3505E24394 for ; Tue, 17 Oct 2017 16:56:00 +0000 (UTC) Date: Tue, 17 Oct 2017 16:56:00 +0000 (UTC) From: "Russell Orf (JIRA)" To: dev@ws.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (WSS-616) STRTransform TransformException when manually adding SAML Assertion via SAMLCallback.setAssertionElement() MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 17 Oct 2017 16:56:07 -0000 [ https://issues.apache.org/jira/browse/WSS-616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Russell Orf updated WSS-616: ---------------------------- 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 that is added via the callback.setAssertionElement() method is not getting searched by the STRParserUtil.getTokenElement() method. was: 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)}} > STRTransform TransformException when manually adding SAML Assertion via SAMLCallback.setAssertionElement() > ---------------------------------------------------------------------------------------------------------- > > Key: WSS-616 > URL: https://issues.apache.org/jira/browse/WSS-616 > Project: WSS4J > Issue Type: Bug > Components: WSS4J Core > Affects Versions: 2.1.7 > Environment: Apache Tomcat 8.0.37 > Reporter: Russell Orf > Assignee: Colm O hEigeartaigh > Labels: security > > 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 that is added via the callback.setAssertionElement() method is not getting searched by the STRParserUtil.getTokenElement() method. -- This message was sent by Atlassian JIRA (v6.4.14#64029) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@ws.apache.org For additional commands, e-mail: dev-help@ws.apache.org