jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lars Krapf (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (JCR-3552) Principal assiocated with Group does not update members
Date Thu, 28 Mar 2013 14:32:15 GMT

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

Lars Krapf commented on JCR-3552:
---------------------------------

User management collects and caches group membership information in the membership provider,
therefore the private field on the principal can be dropped. 
There is no expected log-in performance impact associated with the proposed change, as the
default login-module uses PrincipalProvider.collectGroupMembership() which operates on the
user management directly.

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

Mime
View raw message