I've just tried but it didn't work for me.
Strange issue...
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178878#4178878
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4178878
__
I feel less alone :)
I don't know for the JndiLoginInitialContextFactory.
Thanks for the work around, it works in my case but I cannot use it.
So, I have created a jira issue : https://jira.jboss.org/jira/browse/JBAS-5995
View the original post :
http://www.jboss.com/index.html?module=bb&op=vie
Nobody have a clue?
The EJB Context should be refresh between two calls, right?
The user admin is the first caller of my EJB (so creating the instances) and I
get him as principal name even after logout and login of another user. Are they
any configuration in Jboss concerning this point?
Thanks
I agree and I have read the wiki page.
I tried to set the different options but it didn't solve my problem.
I certainly miss something in the configuration, but I can't figure out what...
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4177699#4177699
Reply to
Thanks for the response ragavgomatam but it didn't work.
I'm using the Jboss 5 RC2 version and I have the same trouble.
Same configuration : a login module performing the authentification on the
client side, the ClientLoginModule on the server side.
I'm using EJB 3 stateless session beans.
So a
I am using Jboss 5 app server and I have some problems when using jaas
authentification.
Different users login and logout successively and call beans methods.
On the client side, I have a custom login module which perform authentification.
On the server side, I use the ClientLoginModule.
In the b
