Hi Ruchith,
I would like to volunteer to implement a policy editor using
rampart.
What I thought was something like this. A policy generator where we can
set what kind of binding policy to use, what tokens to be used and all the
other parameters defined in the WS - Security Policy specification.
Generator
will generate the policy according to parameters defined by the user and use
default values defined in the WS - Security Policy specification when user
has not set any value. It will throw an error when user has not defined a
value
for a mandatory parameter. Generator will be able to generate rampart
policy object and it must also be able to serialize it .
This will be an API level generator and an application sever which
uses
rampart will be able to provide a web interface to it or may be integrate it
with
one of the Axis 2 IDE plugins. This is just my thought and I would like to
know
whether this the correct way to go and what are the improvements that can
be made.
Regards,
Nandana
On 10/13/07, Ruchith Fernando <[EMAIL PROTECTED]> wrote:
>
> Hi Chris,
>
> It is recommended that you use WS-SecurityPolicy based configuration
> with Apache Rampart. We don't have a policy editor yet - any volunteers
> :-) ?. You can use the sample policies we ship with Rampart as a
> starting point.
>
> Thanks,
> Ruchith
>
> Christian Mielke wrote:
> > Hi,
> > it is standard, that WS-Policy is to used with RAMPART. But how do you
> create the policy files? By hand or do you use an editor? Is there a plugin
> for eclipse? I heard about an editor in NETBEANS but I don't use netbeans.
> > Greetings
> > Chris
> >
>
>
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFHEG/TYBHhbS6pedcRAj+EAKCmX2WtIdxHajRnFNM7OuTOHtBfcwCePTST
37lKONmQnCzghnm/X2r0fEg=
=gLxp
-----END PGP SIGNATURE-----
