It tries to propagate the caller security context including the
ClientLoginModule in your login-config.xml. See at
http://wiki.jboss.org/wiki/Wiki.jsp?page=SecurityFAQ
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4039267#4039267
Reply to the post :
http://
I do resolved this problem when ClientLoginModule was included in my
login-config.xml to propagate the caller security context. For more details see
Q3 here http://wiki.jboss.org/wiki/Wiki.jsp?page=SecurityFAQ
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=40
It assumes this context:
1.One ejb jar with one X Stateless .
2.Another ejb jar with Y Stateless.
3.The Security Domain is the same for both.
Well, the login was made for client with user A. At this moment was
performed one method of the X Stateless. In the sequence client perform another
I have one jar with all entity beans, but I need break it in two jars.
When I duplicate the relationship entity classes on the two jars, at
deployment moment of the second jar the application server try to redeploy the
duplicated relationship entity beans.
How I can to resolve th
