If by client side you mean a client running in a VM external to the JBoss
server VM, then this is the expected default behavior. Multi-threaded clients
need to enable the thread local storage mode of the SecurityAssociation
class by either calling SecurityAssociation.setServer() or equivalently
adding a multi-threaded=true option to the JAAS ClientLoginModule config:
other {
org.jboss.security.ClientLoginModule required multi-threaded=true ;
};
----- Original Message -----
From: "Lewis Henderson" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Sunday, May 20, 2001 1:31 PM
Subject: RE: [JBoss-user] Please help :-( tomcat Servlet => Jboss EJB => JAAS
Authentiaction
> ...I tried the three new jars...I get the same problem...However, the
> problem is 'client' side.
>
> Using two machines, both with JBoss & Embedded Tomcat, I connect my browser
> to machine 1 for Tomcat JSP's talking to machine 2's EJB's...
>
> My proxy on the client-side looses the SecurityAssociation as it's threads
> change...
>
> ...am I making sense and is there anything else I can try?
>
>
> Lewis
> -----Original Message-----
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
