You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cxf.apache.org by j2...@op.pl on 2008/08/21 14:35:30 UTC
ws-securitypolicy ws-policy
Hi,
Which versions of this standards will be supported in future versions od CXF?
Regards,
mariusz
Re: ws-securitypolicy ws-policy
Posted by mariuszw <j2...@op.pl>.
dkulp wrote:
>
> On Thursday 21 August 2008 8:35:30 am j2ig4m@op.pl wrote:
>> Which versions of this standards will be supported in future versions od
>> CXF?
>
>>> Right now, for ws-securitypolicy, I'm targetting 1.2. However, the
>>> model
>>> supports 1.1 as well since 1.2 is mostly extensions to 1.1. That said,
>>> the
>>> underlying tools we use (wss4j for example), don't support everything we
>>> need
>>> for full compatibility with some of the ws-security profiles and such.
>>> (xpaths for example)
>
>>> WS-Policy itself is another story. Right now, it only seems to support
>>> the
>>> 1.5 framework. It doesn't recognize the 1.2 framework namespace. I
>>> ran
>>> into this problem pulling some metro based ws-secpol policies into the
>>> tests.
>>> If I get a chance, I may go back and update the ws-p stuff to at least
>>> support the 1.2 namespace.
>
>>> In anycase, I'd be very interesting in any "ws-security policy"
>>> documents/fragments that you might have so I can see what users find
>>> important so I can tackle those first.
>
>>> Any help implementing it would be great too. :-) I'd be more than
>>> happy to
>>> help someone out that would like to dive into some of that code and
>>> contribute. :-)
>
> --
>>>Daniel Kulp
>>>dkulp@apache.org
>>>http://www.dankulp.com/blog
>
>
Thank You for answer.
My task was to write wsdl for my web service with using standards which
works on both ALSB 3.0 and CXF. But ALSB is using is own security policy
standard (namespace: http://www.bea.com/wls90/security/policy). WS-Policy is
from http://schemas.xmlsoap.org/ws/2004/09/policy namespace
Regards,
mariusz
--
View this message in context: http://www.nabble.com/ws-securitypolicy-ws-policy-tp19089256p19196570.html
Sent from the cxf-user mailing list archive at Nabble.com.
Re: ws-securitypolicy ws-policy
Posted by Sergey Beryozkin <se...@iona.com>.
Hi
>> I don't remember exactly how to configure it but please check the CXF
>> WS-Policy config wiki page, there's definitely a way to tell to the policy
>> engine which WS-Policy namespace needs to be recognized...
>
> Is there any reason why it shouldn't just recognize all of them? Definitely
> something we'll probably need to look at. Having to have different Bus's to
> talk to various services that use different versions is definitely not
> ideal. :-(
Agreed. Practically, I'm thinking more of a case where a (remote) consumer and the service provider use different wsp:Policy
namespaces, so if this consumer won't recognize the namespace used by the provider then no policy intersection can occur which,
given that the WS-Policy language hasn't changed significantly across multiple namespaces (it's still Policy, ExactlyOnce, All),
would lead to an otherwise avoidable service communication issue...
Cheers, Sergey
>
> Dan
>
----------------------------
IONA Technologies PLC (registered in Ireland)
Registered Number: 171387
Registered Address: The IONA Building, Shelbourne Road, Dublin 4, Ireland
Re: ws-securitypolicy ws-policy
Posted by Daniel Kulp <dk...@apache.org>.
On Friday 22 August 2008 7:36:07 am Sergey Beryozkin wrote:
> Hi
>
> > WS-Policy itself is another story. Right now, it only seems to support
> > the 1.5 framework. It doesn't recognize the 1.2 framework namespace. I
> > ran into this problem pulling some metro based ws-secpol policies into
> > the tests.
>
> I don't remember exactly how to configure it but please check the CXF
> WS-Policy config wiki page, there's definitely a way to tell to the policy
> engine which WS-Policy namespace needs to be recognized...
Is there any reason why it shouldn't just recognize all of them? Definitely
something we'll probably need to look at. Having to have different Bus's to
talk to various services that use different versions is definitely not
ideal. :-(
Dan
>
> Cheers, Sergey
>
> ----------------------------
> IONA Technologies PLC (registered in Ireland)
> Registered Number: 171387
> Registered Address: The IONA Building, Shelbourne Road, Dublin 4, Ireland
--
Daniel Kulp
dkulp@apache.org
http://www.dankulp.com/blog
Re: ws-securitypolicy ws-policy
Posted by Sergey Beryozkin <se...@iona.com>.
Hi
>
> WS-Policy itself is another story. Right now, it only seems to support the
> 1.5 framework. It doesn't recognize the 1.2 framework namespace. I ran
> into this problem pulling some metro based ws-secpol policies into the tests.
I don't remember exactly how to configure it but please check the CXF WS-Policy config wiki page,
there's definitely a way to tell to the policy engine which WS-Policy namespace needs to be recognized...
Cheers, Sergey
----------------------------
IONA Technologies PLC (registered in Ireland)
Registered Number: 171387
Registered Address: The IONA Building, Shelbourne Road, Dublin 4, Ireland
Re: ws-securitypolicy ws-policy
Posted by Daniel Kulp <dk...@apache.org>.
On Thursday 21 August 2008 8:35:30 am j2ig4m@op.pl wrote:
> Which versions of this standards will be supported in future versions od
> CXF?
Right now, for ws-securitypolicy, I'm targetting 1.2. However, the model
supports 1.1 as well since 1.2 is mostly extensions to 1.1. That said, the
underlying tools we use (wss4j for example), don't support everything we need
for full compatibility with some of the ws-security profiles and such.
(xpaths for example)
WS-Policy itself is another story. Right now, it only seems to support the
1.5 framework. It doesn't recognize the 1.2 framework namespace. I ran
into this problem pulling some metro based ws-secpol policies into the tests.
If I get a chance, I may go back and update the ws-p stuff to at least
support the 1.2 namespace.
In anycase, I'd be very interesting in any "ws-security policy"
documents/fragments that you might have so I can see what users find
important so I can tackle those first.
Any help implementing it would be great too. :-) I'd be more than happy to
help someone out that would like to dive into some of that code and
contribute. :-)
--
Daniel Kulp
dkulp@apache.org
http://www.dankulp.com/blog