You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by Sukma Agung Verdianto <sa...@gmail.com> on 2008/04/24 05:29:08 UTC

Security Policy Subjects

Hi All,
I have question regarding Rampart security policy subjects.
Looking at the example provided by Rampart (sampe02), I see the following
policy is attached under wsdl:service, but in the specs it should be in
wsdl:binding or wsdl:port

    ... ommited parts ...

    <wsdl:service name="sample02">

        <wsp:Policy xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy"
Id="SigOnly">

            <wsp:ExactlyOne>

                <wsp:All>

                    <sp:AsymmetricBinding xmlns:sp="
http://schemas.xmlsoap.org/ws/2005/07/securitypolicy">

... ommited parts ...

                    </sp:SignedParts>

                </wsp:All>

            </wsp:ExactlyOne>

        </wsp:Policy>

    </wsdl:service>

    ... ommited parts ...


Is there any reason why it is there?
We need to know about this since standards is really important for us.
Any advice would be appreciated

Regards,
Sukma

Re: Security Policy Subjects

Posted by Sukma Agung Verdianto <sa...@gmail.com>.
Nandana,

Thanks so much for your valuable response.
Regards,
Sukma

On Thu, Apr 24, 2008 at 2:50 PM, Nandana Mihindukulasooriya <
nandana.cse@gmail.com> wrote:

> Hi Sukma,
>
> Looking at the example provided by Rampart (sampe02), I see the following
> > policy is attached under wsdl:service, but in the specs it should be in
> > wsdl:binding or wsdl:port
> > Is there any reason why it is there?
> >
>
> yes, exactly. This was because of a limitation in Axis2. There was no way
> to specify security policies (in fact, any policy ) at the binding level
> using services.xml.  But this is now fixed and will be available with Axis2
> 1.4 .  We will update the sample accordingly.
>
> thanks,
> /nandana
>
>
>

Re: Security Policy Subjects

Posted by Nandana Mihindukulasooriya <na...@gmail.com>.
Hi Sukma,

Looking at the example provided by Rampart (sampe02), I see the following
> policy is attached under wsdl:service, but in the specs it should be in
> wsdl:binding or wsdl:port
> Is there any reason why it is there?
>

yes, exactly. This was because of a limitation in Axis2. There was no way to
specify security policies (in fact, any policy ) at the binding level using
services.xml.  But this is now fixed and will be available with Axis2 1.4 .
We will update the sample accordingly.

thanks,
/nandana