On 9/25/07, Sanjiva Weerawarana <[EMAIL PROTECTED]> wrote:
>
> balaji hari wrote:
> > Looks like this issue is related with
> >
> >
> http://www.nabble.com/Synapse-proxy-service-changes-service-address-location-tf4209274.html#a11973972
> >
> > Is there a way to specify just not to modify the WSDL port address and
> still
> > change the WSDL to apply security policy?
>
> Um, no :).
>
> The service that Synapse is proxying could be a .Net service or a PHP
> service. The only way to "add value" to the interface offered by that
> service is to front that service with another that offers the same
> interface offered over a more secure policy and which simply delegates the
> actual implementation of the request to the original service. That's
> basically what a proxy service is.
I think you miss interpreted Balaji's requirement. His requirement is to
http proxy synapse so that the proxy service should show the http proxy
address on the wsdl not the synapse server address.
Quoting from Balaji about his requirement,
This is how it looks like.
Forwards
(http)
Apache(https):8081 --------->Synapse(http):6666
So the WSDL should show 8081 rather than 6666.
Thanks,
Ruwan
> Actually the public address to access the web service is different, but we
> > need user name security token policy to be applied to service WSDL.
>
> Right that's possible- just create a proxy and engage whatever policies
> you want on it.
>
> Sanjiva.
> --
> Sanjiva Weerawarana, Ph.D.
> Founder & Director; Lanka Software Foundation; http://www.opensource.lk/
> Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/
> Member; Apache Software Foundation; http://www.apache.org/
> Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
Ruwan Linton
http://www.wso2.org - "Oxygenating the Web Services Platform"
