Return-Path: Delivered-To: apmail-cxf-issues-archive@www.apache.org Received: (qmail 53303 invoked from network); 4 Aug 2010 21:27:41 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 4 Aug 2010 21:27:41 -0000 Received: (qmail 96722 invoked by uid 500); 4 Aug 2010 21:27:41 -0000 Delivered-To: apmail-cxf-issues-archive@cxf.apache.org Received: (qmail 96555 invoked by uid 500); 4 Aug 2010 21:27:40 -0000 Mailing-List: contact issues-help@cxf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cxf.apache.org Delivered-To: mailing list issues@cxf.apache.org Received: (qmail 96301 invoked by uid 99); 4 Aug 2010 21:27:40 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 Aug 2010 21:27:40 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.22] (HELO thor.apache.org) (140.211.11.22) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 Aug 2010 21:27:38 +0000 Received: from thor (localhost [127.0.0.1]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id o74LRG7s017529 for ; Wed, 4 Aug 2010 21:27:16 GMT Message-ID: <10096366.167081280957236554.JavaMail.jira@thor> Date: Wed, 4 Aug 2010 17:27:16 -0400 (EDT) From: "David Valeri (JIRA)" To: issues@cxf.apache.org Subject: [jira] Assigned: (CXF-2928) Add a configuration option that allows STSClient to use the requester's X509Certificate as the SubjectConfirmation KeyInfo data within RequestSecurityToken messages In-Reply-To: <19789932.162821280947277653.JavaMail.jira@thor> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/CXF-2928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Valeri reassigned CXF-2928: --------------------------------- Assignee: David Valeri > Add a configuration option that allows STSClient to use the requester's X509Certificate as the SubjectConfirmation KeyInfo data within RequestSecurityToken messages > -------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: CXF-2928 > URL: https://issues.apache.org/jira/browse/CXF-2928 > Project: CXF > Issue Type: Improvement > Affects Versions: 2.3, 2.2.10 > Reporter: Rich Newcomb > Assignee: David Valeri > Fix For: 2.3, 2.2.10 > > Attachments: cxf-2928-trunk.patch > > > Request to expand the CXF STSClient to support a configuration option that enables an X509Certificate to be used as the saml:SubjectConfirmation KeyInfo element when making a WS-Trust RequestSecurityToken request. > Rationale is as follows: > 1. The SAML 1.1 specification is flexible with regard to the type of XMLSignature KeyInfo (ds:KeyInfo) that may provided in a saml:SubjectConfirmation element to support the holder-of-key confirmation method. > 2. Some relying parties require an X509 Certificate to be provided in the assertion confirmation data in order to perfom validation. For example, any relying party that uses WSS4J version 1.5.8 or earlier for SAML assertion validation (with holder-of-key conf) requires the X509 Certificate to exist in the subject confirmation data. > 3. Accordingly, some STS implementations allow RequestSecurityToken ds:KeyInfo element to optionally contain either a ds:X509Certificate or the corresponding ds:KeyValue for the public key within the RequestSecurityToken message. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.