<br><br><div><span class="gmail_quote">On 10/12/06, <b class="gmail_sendername">Duncan Grisby</b> <<a href="mailto:duncan@grisby.org">duncan@grisby.org</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>> - Adding an authentication token as a Service Context in a *<br>> clientSendRequest* Interceptor.<br><br>This definitely works. I'm using it in production, and it doesn't cause<br>any problems.</blockquote>
<div><br><br>Hello Duncan<br><br>I have hit something of a wall in the above scheme for authentication. I am doing the following:<br><br> 1) Client authenticates to server with username/password<br> 2) Server returns a UUID as security token to client
<br> 3) Client sets UUID as token in service context for subsequent calls to server<br><br>My problem is now how to perform step (4)<br><br> 4) Server matches individual security tokens to distinct clients from different sources
<br><br>I thought to enforce (4) in the "preinvoke" method of a custom servant manager, however I can't find a way to associate individual client requests from different PCs with their individual "authenticated" sessions/connections.
<br><br>Any help is much appreciated.<br><br>Regards<br>Stephan<br> </div><br></div>