Return-Path: X-Original-To: apmail-cxf-dev-archive@www.apache.org Delivered-To: apmail-cxf-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 1B1BCB33C for ; Fri, 20 Jan 2012 10:46:49 +0000 (UTC) Received: (qmail 12205 invoked by uid 500); 20 Jan 2012 10:46:48 -0000 Delivered-To: apmail-cxf-dev-archive@cxf.apache.org Received: (qmail 12112 invoked by uid 500); 20 Jan 2012 10:46:48 -0000 Mailing-List: contact dev-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 dev@cxf.apache.org Received: (qmail 12103 invoked by uid 99); 20 Jan 2012 10:46:47 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 20 Jan 2012 10:46:47 +0000 X-ASF-Spam-Status: No, hits=2.9 required=5.0 tests=HTML_MESSAGE,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [64.95.72.244] (HELO mxout.myoutlookonline.com) (64.95.72.244) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 20 Jan 2012 10:46:40 +0000 Received: from mxout.myoutlookonline.com (localhost [127.0.0.1]) by mxout.myoutlookonline.com (Postfix) with ESMTP id 8609F416BCA for ; Fri, 20 Jan 2012 05:46:18 -0500 (EST) X-Virus-Scanned: by SpamTitan at mail.lan Received: from S10HUB002.SH10.lan (unknown [10.110.2.1]) by mxout.myoutlookonline.com (Postfix) with ESMTP id 13D7B416C09 for ; Fri, 20 Jan 2012 05:46:18 -0500 (EST) Received: from S10BE002.SH10.lan ([::1]) by S10HUB002.SH10.lan ([::1]) with mapi id 14.01.0289.001; Fri, 20 Jan 2012 05:46:17 -0500 From: Andrei Shakirin To: "dev@cxf.apache.org" Subject: Using custom CryptoProvider in Wss4jInInterceptor (patch) Thread-Topic: Using custom CryptoProvider in Wss4jInInterceptor (patch) Thread-Index: AczXYKLhSEpd5i+5QkOFyd7p1rE11g== Date: Fri, 20 Jan 2012 10:46:16 +0000 Message-ID: Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [94.216.84.41] Content-Type: multipart/alternative; boundary="_000_D225CD69196F3F4A9F4174B2FCA06F8858CFAES10BE002SH10lan_" MIME-Version: 1.0 --_000_D225CD69196F3F4A9F4174B2FCA06F8858CFAES10BE002SH10lan_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi, Just a proposal for small improvements in Wss4jInInterceptor. Normally CryptoProvider doesn't instantiated directly via CryptoFactory, bu= t firstly tried to be obtained from message context properties (SecurityCon= stants.ENCRYPT_CRYPTO, SecurityConstants.SIGNATURE_CRYPTO). And only if the= properties are not set, CryptoProvider is instantiated via CryptoFactory. = This gives the possibility to replace Merlin CryptoProvider to custom one (= probably non keystore based). AbstractBindingBuilder, XmlSignHandler, SAMLUtils are working in this way. Unfortunatelly it is not the case for Wss4jInInterceptor. It doesn't initia= lizes crypto provider in RequestData and crypto provider is always created = via CryptoFactory. It makes impossible to use custom implementation of Cryp= toProvider in incoming chain. I have created Jira 4049 with a patch. Regards, Andrei. --_000_D225CD69196F3F4A9F4174B2FCA06F8858CFAES10BE002SH10lan_--