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 "Andrei Dulceanu (Jira)" <ji...@apache.org> on 2021/01/28 10:59:06 UTC

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

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

Andrei Dulceanu closed OAK-9246.
--------------------------------

> 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
>            Priority: Major
>             Fix For: 1.38.0
>
>         Attachments: OAK-9246.patch
>
>
> 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)