Thanks a lot, Nandana. As you can probably guess by yourself, your answer solves my problem. And in a pretty elegant way, if I may add. :-)
Since, this is needed by some new project I'm about to engage, I'll probably be able to use SNAPSHOT version of Rampart. Once again, thank you very much, Pulestar Nunny wrote: > > Hi Pluestar, > Rampart stores all the security information in the Message > Context. > If you can use Rampart SNAPSHOT, then you can easily get the username > using > a property in Message Context. But if you are using Rampart 1.4 or older > version, then you have to parse those security information get the > username. > This blog post [1] describes how retrieve the username from the Message > Context in both cases. > > thanks, > nandana > > [1] - > http://nandana83.blogspot.com/2008/09/accessing-username-used-for.html > > On Thu, Sep 25, 2008 at 2:54 PM, Pulestar <[EMAIL PROTECTED]> wrote: > > [cut] >> -- >> View this message in context: >> http://www.nabble.com/Caller%27s-username-needed-in-regular-service-method--using-Rampart-for-authentication-tp19665961p19665961.html >> Sent from the Axis - User mailing list archive at Nabble.com. >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > > -- > Nandana Mihindukulasooriya > WSO2 inc. > > http://nandana83.blogspot.com/ > http://www.wso2.org > > -- View this message in context: http://www.nabble.com/Caller%27s-username-needed-in-regular-service-method--using-Rampart-for-authentication-tp19665961p19667064.html Sent from the Axis - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
