Re: Best Practices for Handling Client Authentication

Brian Ferris wrote:

> In general, I'm a little reluctant to have my authentication wrapper
> proxies being sent across the wire, but I'm not sure how to avoid it
> in this case.  Any ideas?

These wrapping proxies shouldn't be sent over the wire, even if you make
  your invocation handler part of your downloadable code and they are
designed for serialization things get messy with regard to security issues.

In your case it seems the best thing to do is locate all your 'remote'
code involving the creation of a transaction and execute that as a
wrapped Runnable (it appears you have enough wrappers at hand).

Another option is to rewrite your code that creates the transaction, so
that you create a ServerTransaction that has the 'raw' transaction
manager proxy in it, that should be trivial.
--
Mark

===========================================================================
To unsubscribe, send email to [email protected] and include in the body
of the message "signoff JAVASPACES-USERS".  For general help, send email to
[email protected] and include in the body of the message "help".

To view past JAVASPACES-USERS postings, please see:
http://archives.java.sun.com/archives/javaspaces-users.html