You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@wicket.apache.org by "Igor Vaynberg (JIRA)" <ji...@apache.org> on 2010/02/05 03:44:27 UTC

[jira] Resolved: (WICKET-2715) AuthenticatedWebSession in wicket-auth-roles does thread-unsafe access to signedIn boolean

     [ https://issues.apache.org/jira/browse/WICKET-2715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Igor Vaynberg resolved WICKET-2715.
-----------------------------------

       Resolution: Fixed
    Fix Version/s: 1.4.7
         Assignee: Igor Vaynberg

> AuthenticatedWebSession in wicket-auth-roles does thread-unsafe access to signedIn boolean
> ------------------------------------------------------------------------------------------
>
>                 Key: WICKET-2715
>                 URL: https://issues.apache.org/jira/browse/WICKET-2715
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket-auth-roles
>    Affects Versions: 1.4.6
>            Reporter: Sebastiaan van Erk
>            Assignee: Igor Vaynberg
>             Fix For: 1.4.7
>
>
> Sessions in Wicket must be made thread safe.
> AuthenticatedWebSession in the wicket-auth-roles project is not. It is currently possible that a user clicks logout and this request calls signOut() in one http-thread, and the next request access the page and gets handled via a different thread and still sees the old value of signedIn == true.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.