You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@cxf.apache.org by janb <jb...@talend.com> on 2012/01/16 19:21:52 UTC

Selfmade CryptoProvider

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.

Re: Selfmade CryptoProvider

Posted by Colm O hEigeartaigh <co...@apache.org>.

Hi Jan,

This can't be done currently. You can only use the sig/enc Crypto tags
on the outbound side. I've filed a JIRA here and attached a patch:

https://issues.apache.org/jira/browse/CXF-4034

It depends on a fix in WSS4J 1.6.5 which isn't released yet.

Colm.

On Mon, Jan 16, 2012 at 6:21 PM, janb <jb...@talend.com> wrote:
> 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.



-- 
Colm O hEigeartaigh

Talend Community Coder
http://coders.talend.com