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 2023/01/10 15:40:00 UTC

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=17656681#comment-17656681 ] 

Angela Schreiber commented on OAK-10060:
----------------------------------------

hi [~gknob], thanks for reporting this improvement. you probably are aware of the fact that JCR locking in oak is deprecated. but i admit that the hardcoded lock-break for the admin isn't particularly nice specially in the light of Adobe AEMaaCS. 

since the lock feature is not actively maintained by the oak team it would be good though if your team could come up with a contribution (preferably a PR in git).

> 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)