Return-Path: 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 28E28F1FF for ; Wed, 29 May 2013 15:50:22 +0000 (UTC) Received: (qmail 8606 invoked by uid 500); 29 May 2013 15:50:21 -0000 Delivered-To: apmail-cxf-issues-archive@cxf.apache.org Received: (qmail 8481 invoked by uid 500); 29 May 2013 15:50:21 -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 8441 invoked by uid 99); 29 May 2013 15:50:20 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 29 May 2013 15:50:20 +0000 Date: Wed, 29 May 2013 15:50:20 +0000 (UTC) From: "Syed Abdul Wadood (JIRA)" To: issues@cxf.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (CXF-5046) EncryptedSupportingTokens used with EncryptBeforeSigning does not encrypt Username token MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Syed Abdul Wadood created CXF-5046: -------------------------------------- Summary: EncryptedSupportingTokens used with EncryptBeforeSigning does not encrypt Username token Key: CXF-5046 URL: https://issues.apache.org/jira/browse/CXF-5046 Project: CXF Issue Type: Bug Components: WS-* Components Affects Versions: 2.7.5, 2.6.2 Environment: All platforms Reporter: Syed Abdul Wadood Fix For: 2.6.9, 2.6.8 In some cases, the policy assertion does not encrypt the supporting token. When the policy contains the assertion, and assertions along with the assertion for a username token, the username token is not encrypted in the outbound SOAP message. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira