ode-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Boisvert" <boisv...@intalio.com>
Subject Re: jbi binding authentication question
Date Mon, 02 Jul 2007 03:34:17 GMT
Added in -trunk r552392.

You can register your own message exchange interceptors by adding this
property in ode-axis2.properties:

ode-axis2.mex.interceptors=com.example.MyInterceptor
;com.example.AnotherInterceptor

(and similarly for ode-jbi.properties, with the "ode-jbi" property prefix)

alex


On 7/1/07, Alex Boisvert <boisvert@intalio.com> wrote:
>
> doesn't look like the interceptors are registered (via configuration)
> right now.   i'll get on that.
>
> On 6/29/07, Eduardo Burgos < eburgos@gmail.com> wrote:
> >
> > oh, very nice. How do I use this interceptor? is there any docs?
> >
> >
> >
> > On 6/28/07, Alex Boisvert <boisvert@intalio.com> wrote:
> > >
> > > Actually, you might also consider using a
> > > MessageExchangeInterceptor<
> > > http://svn.apache.org/repos/asf/incubator/ode/trunk/bpel-runtime/src/main/java/org/apache/ode/bpel/intercept/MessageExchangeInterceptor.java
> >
> > > >if
> > > you're not passing the credentials via message data.
> > >
> > > alex
> > >
> > >
> > > On 6/28/07, Alex Boisvert <boisvert@intalio.com > wrote:
> > > >
> > > > 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 <eburgos@gmail.com> 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
> > > > >
> > > >
> > > >
> > >
> >
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message