Greg, Robin, I've just added experimental support for HTTP authentication in the 1.1branch and added a new section<http://cwiki.apache.org/confluence/display/ODExSITE/User+Guide#UserGuide-HTTPAuthentication%2528Axis2%2529>in the user guide to document it: If you're comfortable enough to build Ode, could you give it a try?
I've taken the simple approach of passing a extra message part to carry the authentication credentials. Using partnerLinks or some other form of extension would be cleaner but would have required additional infrastructure. I'd be curious if other developers have feedback on which approach we should adopt for security in general. My sense is that we need way to abstract security protocol concerns out of the BPEL whenever possible. thanks, alex On 9/5/07, Greg Bluntzer <[EMAIL PROTECTED]> wrote: > > > Im sure this has been asked before but I could not understand the answers > on > the forum. > > The partner Link that I'm calling uses the HTTP Header Authorization to > get > Username and Password > > When using soapUI (my soap tester) I can just set the Username and > Password > in the Request Parameters and when it does a post it sends thoses values. > > I'm not sure what I should be doing when Invoking the Partner > Link? Should > the assign be setting some variables or is it even possible to use > security > in ODE? > > Im using Eclipse BPEL to create my BPEL processes > > Thanks for any help or links > > -Greg > -- > View this message in context: > http://www.nabble.com/Passing-in-Login-and-Password-tf4386549.html#a12505870 > Sent from the Apache Ode User mailing list archive at Nabble.com. > >
