Hi Eduardo, It's possible if you're willing to hack the JBI integration layer + bpel_dd and glue things together. There's little infrastructure support for security right now... Perhaps an easier alternative is to write a custom message mapper to set the credentials on the normalized message, and pass the credentials using either special message parts or somehow inject configuration into your message mapper.
alex On 6/28/07, Eduardo Burgos <[EMAIL PROTECTED]> wrote:
Hi, I have a bpel endpoint deployed, it currently invokes a web service that is in a jsr181 serviceunit using the internal jbi binding (I'm using servicemix 3.2-incubating-SNAPSHOT) , the problem is: How can I set a username/password for that invoke (using jbi binding)? I need that in OdeConsumer class, before line 140 ( this line: boolean sendOk = _ode.getChannel().sendSync(inout, _sendSyncTimeout); ) to be able to set the securitySubject to the nmsg message ( nmsg.setSecuritySubject( ... ) ) so that it authenticates when the message arrives the destination jsr181 endpoint. The username/password could be specified at the time you define your partnerlinks in deploy.xml or even if it propagates from securitySubject from the normalizedMessage that activated the process. Either one works for me. Is this possible at the moment? Thanks in advance, Eduardo Burgos
