jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Geoffroy Schneck (JIRA)" <j...@apache.org>
Subject [jira] [Created] (JCR-3704) AbstractPrincipalProvider cachesize is not configurable
Date Mon, 02 Dec 2013 13:48:35 GMT
Geoffroy Schneck created JCR-3704:
-------------------------------------

             Summary: AbstractPrincipalProvider cachesize is not configurable
                 Key: JCR-3704
                 URL: https://issues.apache.org/jira/browse/JCR-3704
             Project: Jackrabbit Content Repository
          Issue Type: Bug
          Components: security
    Affects Versions: 2.7.2
            Reporter: Geoffroy Schneck


The AbstractPrincipalProvider contains a cache, which stores the the mapping of Principal-String
to Principal object; this cache is limited in size by default to 1000 entries.

By default, the init() method where the cache is initialized is called from *org.apache.jackrabbit.core.UserPerWorkspaceSecurityManager*
, always with an empty Properties object :

{code}private PrincipalProviderRegistry getPrincipalProviderRegistry(SessionImpl s) throws
RepositoryException {
        String wspName = s.getWorkspace().getName();
        synchronized (monitor) {
            PrincipalProviderRegistry p = ppRegistries.get(wspName);
           .......

                PrincipalProvider defaultPP = new DefaultPrincipalProvider(systemSession,
(UserManagerImpl) getUserManager(systemSession));
                defaultPP.init(new Properties());
.....
        }
    }{code}

There should be a way to easily define this property.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message