Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Date: Tue, 23 Apr 2013 16:33:16 +0000 (UTC)
From: "angela (JIRA)" <jira@apache.org>
To: dev@jackrabbit.apache.org
Message-ID: <JIRA.12639588.1364480933157.208727.1366734796271@arcas>
In-Reply-To: <JIRA.12639588.1364480933157@arcas>
References: <JIRA.12639588.1364480933157@arcas>
Subject: [jira] [Updated] (JCR-3552) Principal associated with Group does
 not update members
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

angela updated JCR-3552:
------------------------

    Summary: Principal associated with Group does not update members  (was: Principal assiocated with Group does not update members)
    
> Principal associated with Group does not update members
> -------------------------------------------------------
>
>                 Key: JCR-3552
>                 URL: https://issues.apache.org/jira/browse/JCR-3552
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>          Components: jackrabbit-core, security
>            Reporter: Lars Krapf
>            Assignee: angela
>             Fix For: 2.7
>
>         Attachments: jcr3552.patch
>
>
> The Principal associated with a GroupImpl keeps a private member cache, which does not get
> updated after a group membership modification.
> This leads to inconsistencies in combination with default PrincipalProvider that keeps a separate principal cache.

--
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