anonymous wrote : I don't think it's the browser cache, as that would mean you are using cookies? If you are storing their logon in their session, how about this: |
yes, you're right, it's tomcat which stores user principal into session. I solved with a valve which performs the following: 1. flush user cache (see http://wiki.jboss.org/wiki/Wiki.jsp?page=CachingLoginCredentials) 2. reauthenticate user: Realm realm = this.getContainer().getRealm(); | Principal principal = realm.authenticate(username, password); 3. update session: | session.setPrincipal(principal); all this happens transparently to the user thanks everibody, View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3898662#3898662 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3898662 ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
