Return-Path: 
 <issues-return-36042-apmail-cxf-issues-archive=cxf.apache.org@cxf.apache.org>
X-Original-To: apmail-cxf-issues-archive@www.apache.org
Delivered-To: apmail-cxf-issues-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 3E0F81817D
	for <apmail-cxf-issues-archive@www.apache.org>;
 Thu, 22 Oct 2015 19:08:33 +0000 (UTC)
Received: (qmail 31756 invoked by uid 500); 22 Oct 2015 19:08:28 -0000
Delivered-To: apmail-cxf-issues-archive@cxf.apache.org
Received: (qmail 31616 invoked by uid 500); 22 Oct 2015 19:08:28 -0000
Mailing-List: contact issues-help@cxf.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:issues-help@cxf.apache.org>
List-Unsubscribe: <mailto:issues-unsubscribe@cxf.apache.org>
List-Post: <mailto:issues@cxf.apache.org>
List-Id: <issues.cxf.apache.org>
Reply-To: dev@cxf.apache.org
Delivered-To: mailing list issues@cxf.apache.org
Received: (qmail 31565 invoked by uid 99); 22 Oct 2015 19:08:28 -0000
Received: from arcas.apache.org (HELO arcas) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 22 Oct 2015 19:08:28 +0000
Received: from arcas.apache.org (localhost [127.0.0.1])
	by arcas (Postfix) with ESMTP id C15BA2C1F6C
	for <issues@cxf.apache.org>; Thu, 22 Oct 2015 19:08:27 +0000 (UTC)
Date: Thu, 22 Oct 2015 19:08:27 +0000 (UTC)
From: "Grzegorz Maczuga (JIRA)" <jira@apache.org>
To: issues@cxf.apache.org
Message-ID: <JIRA.12906564.1445437244000.32108.1445540907789@Atlassian.JIRA>
In-Reply-To: <JIRA.12906564.1445437244000@Atlassian.JIRA>
References: <JIRA.12906564.1445437244000@Atlassian.JIRA>
 <JIRA.12906564.1445437244673@arcas>
Subject: [jira] [Updated] (CXF-6650) SAML 2.0 SenderVouches / no 2-way TLS /
 XML Signature bug
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394


     [ https://issues.apache.org/jira/browse/CXF-6650?page=3Dcom.atlassian.=
jira.plugin.system.issuetabpanels:all-tabpanel ]

Grzegorz Maczuga updated CXF-6650:
----------------------------------
    Attachment: SAMLwExternalSignature.txt

> SAML 2.0 SenderVouches / no 2-way TLS / XML Signature bug
> ---------------------------------------------------------
>
>                 Key: CXF-6650
>                 URL: https://issues.apache.org/jira/browse/CXF-6650
>             Project: CXF
>          Issue Type: Bug
>    Affects Versions: 3.0.6
>            Reporter: Grzegorz Maczuga
>         Attachments: SAMLwExternalSignature.txt, SAMLwInternalSignature.t=
xt
>
>
> When an Oracle Api Gateway:
> - inserts a SenderVouches SAML 2.0 Assertion=20
> - there is no 2-way TLS connection thus CXF require that both SAML Token =
and SOAP Body are signed by same signature.
> Then CXF server fails to accept such request in following cases:
> 1) when signature is outside SAML Token element then token is considered =
to be not signed by CXF SAMLTokenProcessor
> 2) when signature is inside SAML Token then Signature processing fails as=
 CXF cannot find referenced external Body element
> 3) when signature is inside SAML Token but it only signs SAML and no BODY=
, then it fails Sender-vouches requirements
> Workaround to this is to:
> 1) Set in CXF that =E2=80=9Cnot signed=E2=80=9D SAML is OK:
> <entry key=3D"ws-security.enable.unsigned-saml-assertion.principal" value=
=3D"true" />
> 2) Enforce Signature of SAML on WSDL/WS-SecurityPolicy level:
> <ns3:SignedSupportingTokens>
> =09<ns3:WssSamlV20Token11/>
> </ns3:SignedSupportingTokens>
> but I believe that options 1) and 2) should normally work.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)