Wrong end of the stick with authentication

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Richard Hopwood - 22 Aug 2005 11:03 GMT

I have a feeling I've not quite got it with this WSE authentication.
I'm authentication my users in a custom UsernameTokenManager against a
legacy application we develop. I authenticate by calling a login function in
my app which returns me a session ID, The problem is that once I've come out
of the WSE authentication SoapExtention and into my actual function that is
being called I need to pass that ID in the function call - how do I
comunicate between the authetication layer and the function call?

Thanks
Ric.

Reply to this Message

Pablo Cibraro - 23 Aug 2005 14:50 GMT

Hi Richard,
Maybe this solution can help you:

1. Create a CustomPrincipal deriving from GenericPrincipal
2. Add the SessionId property to that class

In the custom UsernameTokenManager

3. Create a CustomPrincipal object after authenticating to the user in the
custom UsernameTokenManager.
4. Assign the sessionID to that principal
5. Assign the principal to the Thread.CurrentPrincipal property.

In your function

6. Get the CustomPrincipal from the Thread.CurrentPrincipal property
7. Get the SessionId from that principal

I hope this can help you

Regards,
Pablo Cibraro
www.lagash.com

>I have a feeling I've not quite got it with this WSE authentication.
> I'm authentication my users in a custom UsernameTokenManager against a
[quoted text clipped - 9 lines]
> Thanks
> Ric.

Reply to this Message

Richard Hopwood - 23 Aug 2005 15:16 GMT

Thanks, this looks like exactly what I was after.

Ric.

> Hi Richard,
> Maybe this solution can help you:
[quoted text clipped - 33 lines]
> > Thanks
> > Ric.

Reply to this Message

Wrong end of the stick with authentication

Free Magazines