On Tue, Aug 28, 2012 at 8:39 PM, Sameera Jayasoma <same...@wso2.com> wrote:
> Hi Thilini, > > Yeah this helps. Thanks for the reply. So now we have a way to invoke > admin services. But does this mean that we have hard-code the > username/passwords. Is there a way to dynamically set the username and the > password? > No. At the moment you can not set the username/password dynamically. > > Sameera. > > On Tue, Aug 28, 2012 at 12:12 AM, Thilini Ishaka <thil...@wso2.com> wrote: > >> Hi, >> >> This can be done with BPS 3.0.0. Try out with alpha or beta released pack. >> >> You have to add relevant http headers basically the username and >> password via unified endpoints. >> A sample configuration (.epr) is given below. >> >> <wsa:Metadata> >> <id>SInvokeEPR</id> >> <transport type="http"> >> * <authorization-username>adminx</authorization-username> * >> * <authorization-password>adminy</authorization-password> * >> </transport> >> </wsa:Metadata> >> >> FYI: [1] & [2] >> [1] >> https://svn.wso2.org/repos/wso2/carbon/platform/trunk/products/appfactory/modules/bpels/UserCreation/ >> >> [2] >> https://svn.wso2.org/repos/wso2/carbon/platform/trunk/products/appfactory/modules/distribution/product/resources/appfactory/endpoints/UserRegistrationService.epr >> >> >> Hope this helps. >> >> Thanks >> Thilini >> On Tue, Aug 28, 2012 at 12:31 PM, Sameera Jayasoma <same...@wso2.com>wrote: >> >>> Hi Devs, >>> >>> If I put the requirement in another words, how can I add or read HTTP >>> header in a BPEL process. I don't think, BPEL language supports this as >>> this is a transport dependent operation. >>> >>> I've implemented this in 3.2.* release using proxy services for each >>> admin service. These proxy services set the cookie value and invoke admin >>> services. Once you logged in to the AuthenticationAdmin service you get a >>> authenticated cookie and you can use this cookie value can be used for all >>> subsequent invokations. >>> >>> 1. BPEL process invoke the login method in the >>> AuthenticationAdminProxy service which in turn invokes the back-end >>> server's AuthenticationAdmin service. On the return path, this proxy >>> service retrive the authenticated cookie and sent to BPEL as value in the >>> SOAP message so the BPEL can save this value in a variable. >>> 2. For all the subsequent requests from the BPEL process, it send >>> this cookie to the corresponding proxy services. These proxy services set >>> the cookie as a HTTP header and invoke the back-end service. >>> >>> This is kinda hacky solution. But we couldn't find a proper solution at >>> that time. I would like to know whether we can do this properly in latest >>> release. Please let me know. >>> >>> Thanks, >>> Sameera. >>> >>> -- >>> Sameera Jayasoma >>> Senior Technical Lead >>> >>> WSO2, Inc. (http://wso2.com) >>> email: same...@wso2.com >>> blog: http://tech.jayasoma.org >>> >>> Lean . Enterprise . Middleware >>> >>> _______________________________________________ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> *Thilini Ishaka >> WSO2 Inc. http://wso2.com* >> *bolg: thiliniishaka.blogspot.com* >> *linkedin: http://lk.linkedin.com/in/thiliniishaka* >> *twitter: https://twitter.com/#!/ThiliniIsh* >> >> > > > -- > Sameera Jayasoma > Senior Technical Lead > > WSO2, Inc. (http://wso2.com) > email: same...@wso2.com > blog: http://tech.jayasoma.org > > Lean . Enterprise . Middleware > -- *Thilini Ishaka WSO2 Inc. http://wso2.com* *bolg: thiliniishaka.blogspot.com* *linkedin: http://lk.linkedin.com/in/thiliniishaka* *twitter: https://twitter.com/#!/ThiliniIsh*
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
