Seth Ladd wrote:
Hello,
Has anyone done any work to propogate the security context across
remote hessian calls? It seems very straight forward, and wanted to
see if previous work had been done.
Thanks very much,
Seth
Hi Seth
No, it's not yet done.
I was hoping we could automate it so that at th
Ben Alex wrote:
Seth Ladd wrote:
Hello,
Has anyone done any work to propogate the security context across
remote hessian calls? It seems very straight forward, and wanted to
see if previous work had been done.
Thanks very much,
Seth
Hi Seth
No, it's not yet done.
I was hoping we could automate
We implemented a similar sounding audit log several months back (though we no
longer use Hessian) - I'd be interested in seeing what you have. In our case
we needed to audit all service methods invoked (and their parameters) and all
data operations performed (that is, all Hibernate operations).
Andy Depue wrote:
We implemented a similar sounding audit log several months back (though we no
longer use Hessian) - I'd be interested in seeing what you have. In our case
we needed to audit all service methods invoked (and their parameters) and all
data operations performed (that is, all Hibe
Your implementation sounds very similar. We too created an aspect around the
service facade and use thread locals to store the current principal. We also
wanted to keep track of who was calling who (for example, in some situations
it is important for us to know when the client is calling a ser
