Thanks Ruwan.
Appreciate your support!
Manoj
Manoj Priyashan Fernando
Email [email protected]
--- On Wed, 1/7/09, Ruwan Linton <[email protected]> wrote:
> From: Ruwan Linton <[email protected]>
> Subject: Re: Applying security from the ESB to the service
> To: [email protected]
> Date: Wednesday, January 7, 2009, 10:02 PM
> Hi Manoj,
>
> You need to enable security for the outgoing messages, and
> this has been
> explained in the sample 100 [1] as asnkha pointed. You need
> to use the
> following fragment as the send mediator in the inSequence
> of the secure
> proxy that you got to work;
>
> <send>
> <endpoint name="secure">
> <address uri="
> http://localhost:9000/soap/SecureStockQuoteService";>
> <enableSec
> policy="sec_policy"/>
> <enableAddressing/>
> </address>
> </endpoint>
> </send>
>
> Here, the uri and the policy should be changed as
> appropriately.
>
> [1] -
> http://wso2.org/project/esb/java/1.7.1/docs/ESB_Samples.html#Sample100
>
> Thanks,
> Ruwan
>
> On Wed, Jan 7, 2009 at 8:02 PM, Asankha C. Perera
> <[email protected]>wrote:
>
> > Hi Manoj
> >
> >> I could successfuly secure a non-secure service
> using the ESB rampart
> >> config on the policy definition (i.e. ESB decrypts
> a client encrypted
> >> message before passing to a non-secure service).
> >> Now I want to extend on this so that ESB will
> re-apply a different level
> >> of security (i.e. re-encrypt the message leaving
> the ESB to a secure service
> >> using another key on the ESB keystore).
> >> What is the proper way to do this?
> >>
> > This is trivial, see
> >
> http://synapse.apache.org/Synapse_Samples.html#Sample100
> >
> > Just use one policy for messages coming into the
> proxy, and use one [or
> > more] other policies for your endpoint[s]
> >
> > cheers
> > asankha
> >
> > --
> > Asankha C. Perera
> > http://adroitlogic.org
> >
> > http://esbmagic.blogspot.com
> >
> >
>
>
> --
> Ruwan Linton
> http://wso2.org - "Oxygenating the Web Services
> Platform"
> http://ruwansblog.blogspot.com/
