Return-Path: 
 <dev-return-11891-apmail-cxf-dev-archive=cxf.apache.org@cxf.apache.org>
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 ABCF7BDF5
	for <apmail-cxf-dev-archive@www.apache.org>;
 Mon, 16 Jan 2012 18:22:21 +0000 (UTC)
Received: (qmail 38582 invoked by uid 500); 16 Jan 2012 18:22:21 -0000
Delivered-To: apmail-cxf-dev-archive@cxf.apache.org
Received: (qmail 38519 invoked by uid 500); 16 Jan 2012 18:22:20 -0000
Mailing-List: contact dev-help@cxf.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@cxf.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@cxf.apache.org>
List-Post: <mailto:dev@cxf.apache.org>
List-Id: <dev.cxf.apache.org>
Reply-To: dev@cxf.apache.org
Delivered-To: mailing list dev@cxf.apache.org
Received: (qmail 38510 invoked by uid 99); 16 Jan 2012 18:22:20 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 16 Jan 2012 18:22:20 +0000
X-ASF-Spam-Status: No, hits=2.0 required=5.0
	tests=SPF_NEUTRAL,URI_HEX
X-Spam-Check-By: apache.org
Received-SPF: neutral (nike.apache.org: local policy)
Received: from [216.139.236.26] (HELO sam.nabble.com) (216.139.236.26)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 16 Jan 2012 18:22:13 +0000
Received: from [192.168.236.26] (helo=sam.nabble.com)
	by sam.nabble.com with esmtp (Exim 4.72)
	(envelope-from <jbernhardt@talend.com>)
	id 1RmrBo-0006bo-Bo
	for dev@cxf.apache.org; Mon, 16 Jan 2012 10:21:52 -0800
Date: Mon, 16 Jan 2012 10:21:52 -0800 (PST)
From: janb <jbernhardt@talend.com>
To: dev@cxf.apache.org
Message-ID: <1326738112357-5149491.post@n5.nabble.com>
Subject: Selfmade CryptoProvider
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Virus-Checked: Checked by ClamAV on apache.org

Hi @all,

I'm testing a custom cryptoProvider (XKMS Support) and try to get it
running. But it seems to me, that CXF has never tested this case before...
Hopefully you can help me!

Here is what I try to do:

1. I set the following properties:
<jaxws:endpoint ... >
<jaxws:properties>
	...
	<entry key="ws-security.signature.crypto" value-ref="xkmsCryptoProvider"/>
	<entry key="ws-security.encryption.crypto" value-ref="xkmsCryptoProvider"/>
	...
</jaxws:properties>
	...
</jaxws:endpoint>

I do not set any "ws-security.signature.properties" nor
"ws-security.encryption.properties", because I need to wire another bean to
my cryptoProvider and I can not get this done via properties.

When I try to test my code it is never called... After debugging for a while
I could only find several point where the property files are read but none
where my crypto provider is set via key="ws-security.signature.crypto". Am I
only blind or this this really a missing feature?

On this side under "Configuring the extra properties" it states, that I
could use my own provider just be using these properties... This feature is
very important to me!! What can I do?

Best regards
Jan

--
View this message in context: http://cxf.547215.n5.nabble.com/Selfmade-CryptoProvider-tp5149491p5149491.html
Sent from the cxf-dev mailing list archive at Nabble.com.