Since we clean the threadlocal after each requests, the issue is solved.
We used a main filter which encapsulates the request processing and at
the end of the filter, we set the threadlocal to null.
something like :
public void doFilter(..) throws .. {
HttpServletRequest req = (HttpServle
Caldarale, Charles R a écrit :
>> From: Pierrick Terrettaz [mailto:[EMAIL PROTECTED]
>> Subject: Re: realm login and user session are not the same
>>
>> We are also using a ThreadLocal static reference in a class
>> to store the request.getUserPrincipal() to g
> From: Pierrick Terrettaz [mailto:[EMAIL PROTECTED]
> Subject: Re: realm login and user session are not the same
>
> We are also using a ThreadLocal static reference in a class
> to store the request.getUserPrincipal() to give the current
> username to beans which are not acc
Caldarale, Charles R a écrit :
>> From: Pierrick Terrettaz [mailto:[EMAIL PROTECTED]
>> Subject: realm login and user session are not the same
>>
>> When a user logs in through the realm authentification
>> FORM method in the website, the username and login are
>> well checked but the user com
> From: Pierrick Terrettaz [mailto:[EMAIL PROTECTED]
> Subject: realm login and user session are not the same
>
> When a user logs in through the realm authentification
> FORM method in the website, the username and login are
> well checked but the user come in with the session of
> an other u
