excuse me.
I am totally lost in your description.
I don't see your point. It seems like you just want to figure out how to
pass *an identity* to a remote computer.
First, the *authenticate a thread with acegi *thing really make me confused,
how to do that? where is the *identity *from? Acegi generates it? Then you
present it to a remote Acegi and just try to get a authenticated thread?
That is your purpose? Using acegi to transfer an *authenticated thread
object*?
On 8/26/07, Billy Newport <[EMAIL PROTECTED]> wrote:
>
>
> I have a transport that I'd like to integrate with acegi. A JVM will
> authenticate a thread with acegi resulting in an identity being associated
> with that thread. If that thread makes a remote call (using an arbitrary
> RPC protocol) how do I convert the current identity to a serializable
> token
> that can be presented to acegi on the remote JVM to be reapplied to the
> dispatch thread there?
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems? Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> Home: http://acegisecurity.org
> Acegisecurity-developer mailing list
> Acegisecurity-developer@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/acegisecurity-developer
>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Home: http://acegisecurity.org
Acegisecurity-developer mailing list
Acegisecurity-developer@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/acegisecurity-developer
