I believe that I have a working solution (tests seems to be conclusive). Let me know if this makes senses.
1) Create a custom principal class holding user name and an extra "id" attribute. 2) Create a custom login module for the client. This custom login module is requesting only user name and password, and is generating a new unique id string for each new "login". It then creates an instance of the custom principal and put it in the share state. 3) The JAAS configuration on the client is composed of my custom login module first, then the JBoss client login module with password-stacking on in order to reuse the custom principal created with my custom login module. It seems to work fine and it seems to be confirmed when I looked at the code of the TimedCachePolicy. The hashcode of the principal sent from the client is the real key of the authorization cache. So, provided that I define the proper hashCode method taking into account the uniquely generated id, that should do it. Thomas View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3877055#3877055 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3877055 ------------------------------------------------------- This SF.Net email is sponsored by: NEC IT Guy Games. Get your fingers limbered up and give it your best shot. 4 great events, 4 opportunities to win big! Highest score wins.NEC IT Guy Games. Play to win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
