Hi Ruchith, I looked at the website and understand how to fetch the username from the message context. I'm afraid the problem doesn't change however.
Because when the message receiver method is reached the security handler is not processed. Sandesha has called the handler in the create sequence call, so won't call the security handler when it resumes application messages of a RM sequence. In other words there is no user information in the message context. Thanks, Lennard. ----- Original Message ----- From: Ruchith Fernando <[EMAIL PROTECTED]> Date: Thursday, August 3, 2006 3:46 pm Subject: Re: [Axis2] Sandesha2 and Rampart module > On 8/3/06, Chamikara Jayalath <[EMAIL PROTECTED]> wrote: > > Hi Lennard, > > > > Please see my comments below, > > > > > > > > On 8/3/06, L YSSELSTEIN <[EMAIL PROTECTED]> wrote: > > > Hi Chamikara, > > > > > > > Basically, what we are trying to do is this. When the first > invocation> passes the security handler, the handler checks the > user credentials. > > If the username/password is valid, the userprofile is retrieved > from Ldap > > and stored in a context for future reference. > > > > From the security handler we cannot store it in the message > context. The > > callback interface does not give a handle to the message context. > > > > This leaves us with the following questions. > > How can we store the userprofile in the current messagecontext? > > > > > > I guess ruchith will answer this. > > Its true that you don't have access to the message context in the > callback handler. But the security processing results are stored in > the message context and you can retrieve them as shown here: > > http://www.wso2.net/kb/169 > > Therefore you will be able to get the user context from the LDAP store > later in a handler. > > > Thanks, > Ruchith > > -- > www.ruchith.org > > -------------------------------------------------------------------- > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
