You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2013/07/16 11:20:50 UTC

[jira] [Commented] (SLING-2966) Insufficient synchronization in SlingAuthenticator

    [ https://issues.apache.org/jira/browse/SLING-2966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13709630#comment-13709630 ] 

Carsten Ziegeler commented on SLING-2966:
-----------------------------------------

The problem is that the changed operation is not performed atomar but in two steps.
                
> Insufficient synchronization in SlingAuthenticator
> --------------------------------------------------
>
>                 Key: SLING-2966
>                 URL: https://issues.apache.org/jira/browse/SLING-2966
>             Project: Sling
>          Issue Type: Bug
>          Components: Authentication
>    Affects Versions: Auth Core 1.1.2
>            Reporter: Lars Krapf
>            Assignee: Carsten Ziegeler
>              Labels: authentication, sling
>             Fix For: Auth Core 1.1.4
>
>         Attachments: sling_authenticator.patch
>
>
> In the serviceChanged method of SlingAuthenticator a service is removed and subsequently re-added in case of a modification event. This can lead to synchronization problems (e.g. remove, remove, add, add) if two threads trigger this handler at the same time (e.g. duplication of CUG roots in the holder-cache of the CQ CUG handler after activation of a page with alias).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira