You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-issues@jackrabbit.apache.org by "Angela Schreiber (Jira)" <ji...@apache.org> on 2020/09/30 13:51:00 UTC

[jira] [Created] (OAK-9246) Avoid hardcoding stats classes in SecurityProviderRegistration

Angela Schreiber created OAK-9246:
-------------------------------------

             Summary: Avoid hardcoding stats classes in SecurityProviderRegistration
                 Key: OAK-9246
                 URL: https://issues.apache.org/jira/browse/OAK-9246
             Project: Jackrabbit Oak
          Issue Type: Improvement
          Components: core, security, security-spi
            Reporter: Angela Schreiber
            Assignee: Angela Schreiber


OAK-8102 introduce a single {{LoginModuleStats}} to collect unexpected errors during the repository login. the corresponding monitor and mbeans are registered in the {{SecurityProviderRegistration}} after creating the {{SecurityProvider}} instance.

instead of 'hardcoding' the stats in {{SecurityProviderRegistration}}, i would suggest to come up with a mechanism that allows individual security modules to register statistics related monitors and mbeans as needed. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)