-
1. Re: JBoss authentication cache problem
kwstasm Apr 25, 2007 11:31 AM (in response to kwstasm)"kwstasm" wrote:
Hi
... to remote from a remote machine ...
this should be login from a remote machine -
2. Re: JBoss authentication cache problem
jaikiran Apr 25, 2007 12:28 PM (in response to kwstasm)Looks like cookies are enabled in your browser. Try disabling cookies and see if it works.
-
3. Re: JBoss authentication cache problem
jaikiran Apr 25, 2007 12:30 PM (in response to kwstasm)Also try clearing out the browser cache of your second browser instance, before accessing the application
-
4. Re: JBoss authentication cache problem
kwstasm Apr 26, 2007 5:06 AM (in response to kwstasm)No luck.
The same happens even if the second instance is a Firefox instance. -
5. Re: JBoss authentication cache problem
jaikiran Apr 26, 2007 9:48 AM (in response to kwstasm)Can you get the jboss security package TRACE logs. That might give a hint. Have a look at Q4 at http://wiki.jboss.org/wiki/Wiki.jsp?page=SecurityFAQ to obtain the logs
-
6. Re: JBoss authentication cache problem
sim-smith Apr 26, 2007 6:02 PM (in response to kwstasm)As far as I am aware, it isn't possible. The JBoss caching mechanism doesn't/can't distinguish between where the authentication request comes from - e.g. a new browser session vs. new page request vs. EJB call. You can try setting the timeout to 1 second, which would effectively force every page request to hit the LoginModule again, or to 0 seconds which would cause every authentication request (including EJB calls) to hit the login module.
-
7. Re: JBoss authentication cache problem
kwstasm Apr 26, 2007 11:59 PM (in response to kwstasm)I see.
I decided to set the DefaultCacheTimeout to 0 and just ignore the credential
check when the user has already logged in.
Thank you for your answers.