You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cxf.apache.org by "Penmatsa, Vinay" <vi...@sap.com> on 2011/11/14 20:06:42 UTC
InitiatorSignatureToken
Hi,
A service that I need to use has the following policy definition:
<sp:AsymmetricBinding xmlns:sp="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702">
<wsp:Policy>
<sp:InitiatorSignatureToken>
<wsp:Policy>
<sp:X509Token sp:IncludeToken="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702/IncludeToken/AlwaysToRecipient">
<wsp:Policy>
<sp:WssX509V3Token10 />
</wsp:Policy>
</sp:X509Token>
</wsp:Policy>
</sp:InitiatorSignatureToken>
....
....
</sp:AsymmetricBinding>
CXF could not process because it seems it didn't expect "InitiatorSignatureToken" element.
I get the warning:
org.apache.cxf.ws.policy.AssertionBuilderRegistryImpl handleNoRegisteredBuilder
WARNING: No assertion builder for type {http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702}InitiatorSignatureToken registered.
Is this wrong policy definition or CXF limitation? or did I miss something?
Regards,
Vinay
Re: InitiatorSignatureToken
Posted by Daniel Kulp <dk...@apache.org>.
On Tuesday, December 06, 2011 2:09:57 PM Penmatsa, Vinay wrote:
> Hi,
> Submitted a patch for this in 2.4.x : CXF-3960
> Should I keep the status/resolution in open/unresolved?
Yea. When Colm or someone looks at the patch and commits it, they'll adjust
the status.
Dan
>
> -Vinay
>
> -----Original Message-----
> From: Colm O hEigeartaigh [mailto:coheigea@apache.org]
> Sent: Tuesday, November 15, 2011 4:30 AM
> To: users@cxf.apache.org
> Subject: Re: InitiatorSignatureToken
>
> Hi Vinay,
>
> IntiatorSignatureToken is not currently supported. If you want to
> provider a patch I suggest looking at how the AsymmetricBindingBuilder
> builds the AsymmetricBinding policy model - it should be easy enough
> to add support for InitiatorSignatureToken here. The trickier task
> will be to add support to the AsymmetricBindingHandler to use this
> policy.
>
> Colm.
>
> On Mon, Nov 14, 2011 at 7:21 PM, Penmatsa, Vinay <vi...@sap.com>
wrote:
> > I'm running CXF 2.4.1.
> > I do not see implementation or builder for IntiatorSignatureToken.
> > Should I do it myself?
> >
> > -Vinay
> >
> >
> > -----Original Message-----
> > From: Penmatsa, Vinay [mailto:vinay.penmatsa@sap.com]
> > Sent: Monday, November 14, 2011 2:07 PM
> > To: users@cxf.apache.org
> > Subject: InitiatorSignatureToken
> >
> > Hi,
> > A service that I need to use has the following policy definition:
> > <sp:AsymmetricBinding
> > xmlns:sp="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702">
> > <wsp:Policy>
> > <sp:InitiatorSignatureToken>
> > <wsp:Policy>
> > <sp:X509Token
> > sp:IncludeToken="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200
> > 702/IncludeToken/AlwaysToRecipient"> <wsp:Policy>
> > <sp:WssX509V3Token10 />
> > </wsp:Policy>
> > </sp:X509Token>
> > </wsp:Policy>
> > </sp:InitiatorSignatureToken>
> > ....
> > ....
> > </sp:AsymmetricBinding>
> >
> > CXF could not process because it seems it didn't expect
> > "InitiatorSignatureToken" element. I get the warning:
> > org.apache.cxf.ws.policy.AssertionBuilderRegistryImpl
> > handleNoRegisteredBuilder WARNING: No assertion builder for type
> > {http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702}InitiatorSig
> > natureToken registered.
> >
> > Is this wrong policy definition or CXF limitation? or did I miss
> > something?
> >
> > Regards,
> > Vinay
--
Daniel Kulp
dkulp@apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com
RE: InitiatorSignatureToken
Posted by "Penmatsa, Vinay" <vi...@sap.com>.
Hi,
Submitted a patch for this in 2.4.x : CXF-3960
Should I keep the status/resolution in open/unresolved?
-Vinay
-----Original Message-----
From: Colm O hEigeartaigh [mailto:coheigea@apache.org]
Sent: Tuesday, November 15, 2011 4:30 AM
To: users@cxf.apache.org
Subject: Re: InitiatorSignatureToken
Hi Vinay,
IntiatorSignatureToken is not currently supported. If you want to
provider a patch I suggest looking at how the AsymmetricBindingBuilder
builds the AsymmetricBinding policy model - it should be easy enough
to add support for InitiatorSignatureToken here. The trickier task
will be to add support to the AsymmetricBindingHandler to use this
policy.
Colm.
On Mon, Nov 14, 2011 at 7:21 PM, Penmatsa, Vinay <vi...@sap.com> wrote:
> I'm running CXF 2.4.1.
> I do not see implementation or builder for IntiatorSignatureToken. Should I do it myself?
>
> -Vinay
>
>
> -----Original Message-----
> From: Penmatsa, Vinay [mailto:vinay.penmatsa@sap.com]
> Sent: Monday, November 14, 2011 2:07 PM
> To: users@cxf.apache.org
> Subject: InitiatorSignatureToken
>
> Hi,
> A service that I need to use has the following policy definition:
> <sp:AsymmetricBinding xmlns:sp="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702">
> <wsp:Policy>
> <sp:InitiatorSignatureToken>
> <wsp:Policy>
> <sp:X509Token sp:IncludeToken="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702/IncludeToken/AlwaysToRecipient">
> <wsp:Policy>
> <sp:WssX509V3Token10 />
> </wsp:Policy>
> </sp:X509Token>
> </wsp:Policy>
> </sp:InitiatorSignatureToken>
> ....
> ....
> </sp:AsymmetricBinding>
>
> CXF could not process because it seems it didn't expect "InitiatorSignatureToken" element.
> I get the warning:
> org.apache.cxf.ws.policy.AssertionBuilderRegistryImpl handleNoRegisteredBuilder
> WARNING: No assertion builder for type {http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702}InitiatorSignatureToken registered.
>
> Is this wrong policy definition or CXF limitation? or did I miss something?
>
> Regards,
> Vinay
>
>
>
--
Colm O hEigeartaigh
Talend Community Coder
http://coders.talend.com
Re: InitiatorSignatureToken
Posted by Colm O hEigeartaigh <co...@apache.org>.
Hi Vinay,
IntiatorSignatureToken is not currently supported. If you want to
provider a patch I suggest looking at how the AsymmetricBindingBuilder
builds the AsymmetricBinding policy model - it should be easy enough
to add support for InitiatorSignatureToken here. The trickier task
will be to add support to the AsymmetricBindingHandler to use this
policy.
Colm.
On Mon, Nov 14, 2011 at 7:21 PM, Penmatsa, Vinay <vi...@sap.com> wrote:
> I'm running CXF 2.4.1.
> I do not see implementation or builder for IntiatorSignatureToken. Should I do it myself?
>
> -Vinay
>
>
> -----Original Message-----
> From: Penmatsa, Vinay [mailto:vinay.penmatsa@sap.com]
> Sent: Monday, November 14, 2011 2:07 PM
> To: users@cxf.apache.org
> Subject: InitiatorSignatureToken
>
> Hi,
> A service that I need to use has the following policy definition:
> <sp:AsymmetricBinding xmlns:sp="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702">
> <wsp:Policy>
> <sp:InitiatorSignatureToken>
> <wsp:Policy>
> <sp:X509Token sp:IncludeToken="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702/IncludeToken/AlwaysToRecipient">
> <wsp:Policy>
> <sp:WssX509V3Token10 />
> </wsp:Policy>
> </sp:X509Token>
> </wsp:Policy>
> </sp:InitiatorSignatureToken>
> ....
> ....
> </sp:AsymmetricBinding>
>
> CXF could not process because it seems it didn't expect "InitiatorSignatureToken" element.
> I get the warning:
> org.apache.cxf.ws.policy.AssertionBuilderRegistryImpl handleNoRegisteredBuilder
> WARNING: No assertion builder for type {http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702}InitiatorSignatureToken registered.
>
> Is this wrong policy definition or CXF limitation? or did I miss something?
>
> Regards,
> Vinay
>
>
>
--
Colm O hEigeartaigh
Talend Community Coder
http://coders.talend.com
RE: InitiatorSignatureToken
Posted by "Penmatsa, Vinay" <vi...@sap.com>.
I'm running CXF 2.4.1.
I do not see implementation or builder for IntiatorSignatureToken. Should I do it myself?
-Vinay
-----Original Message-----
From: Penmatsa, Vinay [mailto:vinay.penmatsa@sap.com]
Sent: Monday, November 14, 2011 2:07 PM
To: users@cxf.apache.org
Subject: InitiatorSignatureToken
Hi,
A service that I need to use has the following policy definition:
<sp:AsymmetricBinding xmlns:sp="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702">
<wsp:Policy>
<sp:InitiatorSignatureToken>
<wsp:Policy>
<sp:X509Token sp:IncludeToken="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702/IncludeToken/AlwaysToRecipient">
<wsp:Policy>
<sp:WssX509V3Token10 />
</wsp:Policy>
</sp:X509Token>
</wsp:Policy>
</sp:InitiatorSignatureToken>
....
....
</sp:AsymmetricBinding>
CXF could not process because it seems it didn't expect "InitiatorSignatureToken" element.
I get the warning:
org.apache.cxf.ws.policy.AssertionBuilderRegistryImpl handleNoRegisteredBuilder
WARNING: No assertion builder for type {http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702}InitiatorSignatureToken registered.
Is this wrong policy definition or CXF limitation? or did I miss something?
Regards,
Vinay