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 (JIRA)" <ji...@apache.org> on 2016/06/10 08:55:20 UTC

[jira] [Updated] (OAK-4460) Bogus lock token

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

angela updated OAK-4460:
------------------------
    Priority: Blocker  (was: Major)

> Bogus lock token
> ----------------
>
>                 Key: OAK-4460
>                 URL: https://issues.apache.org/jira/browse/OAK-4460
>             Project: Jackrabbit Oak
>          Issue Type: Technical task
>          Components: jcr
>            Reporter: angela
>            Priority: Blocker
>             Fix For: 1.6
>
>
> The current implementation uses the node's path a lock token which is IMHO totally bogus and defeats the purpose as it means that every single session can easily become lock-holder by just adding the nodes path as lock token to the session.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)