You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Geoffroy Schneck (JIRA)" <ji...@apache.org> on 2013/12/02 14:48:35 UTC

[jira] [Created] (JCR-3704) AbstractPrincipalProvider cachesize is not configurable

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)