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 E48AC17C43 for ; Tue, 22 Sep 2015 11:57:20 +0000 (UTC) Received: (qmail 70075 invoked by uid 500); 22 Sep 2015 11:57:04 -0000 Delivered-To: apmail-cxf-issues-archive@cxf.apache.org Received: (qmail 70034 invoked by uid 500); 22 Sep 2015 11:57:04 -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 70022 invoked by uid 99); 22 Sep 2015 11:57:04 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 22 Sep 2015 11:57:04 +0000 Date: Tue, 22 Sep 2015 11:57:04 +0000 (UTC) From: =?utf-8?Q?Stefan_Pr=C3=B6ls_=28JIRA=29?= To: issues@cxf.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CXF-6582) Support newer symmetric signature algorithms with WS-SecurityPolicy 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-6582?page=3Dcom.atlassian.j= ira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D149024= 48#comment-14902448 ]=20 Stefan Pr=C3=B6ls commented on CXF-6582: ----------------------------------- But right that doesn't have any effect for me in 3.1.3. See also CXF-6582 and CXF-5200. You can find an example WSDL illustrating t= he problem in my comment to CXF-5200. It _almost_ works with your latest changes in 3.1.3, but there are two prob= lems remaining: 1. Basic256Sha256 in the AlgorithmSuite as no effect. I can live with that as there are the ws-security.(a)symmetric.signature.al= gorithm properties to set SHA-256 explicitly. 2. While the ws-security.(a)symmetric.signature.algorithm properties set th= e SignatureMethod just fine, it does not influence the DigestMethods of the= signatures' references. CXF keeps using SHA-1 here, even when the Signatur= eMethod is set to HMAC-SHA256 using the ws-security.symmetric.signature.alg= orithm property. > Support newer symmetric signature algorithms with WS-SecurityPolicy > ------------------------------------------------------------------- > > Key: CXF-6582 > URL: https://issues.apache.org/jira/browse/CXF-6582 > Project: CXF > Issue Type: Bug > Reporter: Colm O hEigeartaigh > Assignee: Colm O hEigeartaigh > Fix For: 3.1.3, 3.0.7 > > > This task is to support using symmetric signature algorithms other than t= he default (HMAC-SHA1) with WS-SecurityPolicy. -- This message was sent by Atlassian JIRA (v6.3.4#6332)