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 "Marcel Reutegger (Jira)" <ji...@apache.org> on 2023/01/13 14:36:00 UTC

[jira] [Resolved] (OAK-10060) Add ability to configure which principals could break a jcr:lock

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

Marcel Reutegger resolved OAK-10060.
------------------------------------
    Fix Version/s:     (was: 1.48.0)
       Resolution: Won't Fix

Resolving as WONTFIX. Please re-open if you disagree and give a reason why the workaround  is not good enough.

> Add ability to configure which principals could break a jcr:lock
> ----------------------------------------------------------------
>
>                 Key: OAK-10060
>                 URL: https://issues.apache.org/jira/browse/OAK-10060
>             Project: Jackrabbit Oak
>          Issue Type: Story
>          Components: jcr
>            Reporter: Gilles Knobloch
>            Priority: Major
>
> Today, the "admin" user only can break a lock.
> It would help if we'd have the ability to configure more users/groups who would be able to do this, and not depend on a single super user.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)