Looking further at this it seems that the way to do this would be to have the Principal and credentials stored in the MBean and then have the MBean set them on the SecurityAssociation on the thread that is going to call the ejb. Am I right in thinking that this now has nothing todo with using JAAS or not?
My question now is then (in addition to the - is this a stupid idea?) do I need to "unset" the principal and credentials on the SecurityAssociation by passing nulls when the execution has finished? I cant see anything in SecurityInterceptor doing that, but I would have thought it would have been a good idea. I assume that the approach is to set it every time so that the last one is overridden? cheesr dim On Mon, 15 Oct 2001, Dmitri Colebatch wrote: > hey list, > > I'm got a requirement for something that would allow a session > ejb to be invoked asynchronously by another bean. I'm looking at > the following options: > > - MDB proxy style design > - MBean service with worker threads > > MDB: > doesn't provide any context propagation, as per spec, requires > parameters to be serializable > > MBean: > obviously not going to provide tx propagation, but I was wondering if > there is some way that I could get the security to propagate? I'll be > writing my own JAAS security context anyway, so I was thinking that there > would probably be some way that I could have the security context > propegate, or at least re-instated for the next call. > > here's what I'm thinking: > > 1. call enters container through servlet > 2. servlet calls bean > 3. security context is set (this is where this happens yes?) > 4. bean calls async service and passes information required to make > other calls including current principal > 5. bean returns > > 6. mbean service sets security context for call before calling bean 2 > > does that make sense? is the whole idea stupid? is there something that > already does this? > > an answer to any of the above would be great (o: > > cheers, and thanks > dim > > > _______________________________________________ > JBoss-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-user > _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
