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 9CEF9200C45 for ; Tue, 28 Mar 2017 09:08:45 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 9B79F160B7E; Tue, 28 Mar 2017 07:08:45 +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 DFFF3160B89 for ; Tue, 28 Mar 2017 09:08:44 +0200 (CEST) Received: (qmail 90451 invoked by uid 500); 28 Mar 2017 07:08:44 -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 90434 invoked by uid 99); 28 Mar 2017 07:08:43 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 28 Mar 2017 07:08:43 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 66C091A0790 for ; Tue, 28 Mar 2017 07:08:43 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -97.889 X-Spam-Level: X-Spam-Status: No, score=-97.889 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URI_HEX=1.313, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id 5cNwLuNg74jE for ; Tue, 28 Mar 2017 07:08:42 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 70A9D5FD00 for ; Tue, 28 Mar 2017 07:08:42 +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 E7EEDE06B9 for ; Tue, 28 Mar 2017 07:08:41 +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 9436125CDE for ; Tue, 28 Mar 2017 07:08:41 +0000 (UTC) Date: Tue, 28 Mar 2017 07:08:41 +0000 (UTC) From: "Colm O hEigeartaigh (JIRA)" To: issues@cxf.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Assigned] (CXF-4028) X509TokenValidator uses signature-crypto-provider instead of encryption-crypto-provider MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 28 Mar 2017 07:08:45 -0000 [ https://issues.apache.org/jira/browse/CXF-4028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh reassigned CXF-4028: ---------------------------------------- Assignee: Colm O hEigeartaigh (was: Alessio Soldano) > X509TokenValidator uses signature-crypto-provider instead of encryption-crypto-provider > --------------------------------------------------------------------------------------- > > Key: CXF-4028 > URL: https://issues.apache.org/jira/browse/CXF-4028 > Project: CXF > Issue Type: Bug > Components: WS-* Components > Affects Versions: 2.5 > Reporter: Jan Bernhardt > Assignee: Colm O hEigeartaigh > Fix For: 3.1.11, 3.2.0 > > Original Estimate: 4h > Remaining Estimate: 4h > > I found a bug in X509TokenValidator class. > There are two crypto handler which can be configured: > > > ws-security.signature.crypto is for my own signature, when sending messages, and to decrypt messages, which have been send to me. (here is my private key) > ws-security.encryption.crypto is for encrypting messages before sending and validating of signatures in received messages. (here are all my trusted public keys/CAs) > In X509TokenValidator the signature crypto provider is used to validate a received message signature. But instead the encryption provider should be used! See line 101 in X509TokenValidator.java: > Crypto sigCrypto = stsProperties.getSignatureCrypto(); > There might be other sections which needs to be updated as well... > Best regards > Jan > See post on the mailinglist regarding this topic also: > http://cxf.547215.n5.nabble.com/X509TokenValidator-td5139681.html -- This message was sent by Atlassian JIRA (v6.3.15#6346)