After review and refactor hard-locking module, we decided to use JCR native lock support instead of hooking into MagnoliaAccessProvider and provide the custom implementation for locking. This helps end user not to configure their repository access provider anymore and simplify the implementation a lot. However this lead to an issue that:

By using JCR native lock for hard-locking module, user who locked the page cannot edit the page anymore because it is JCR designed purpose. Who lock the item can have the lock token to unlock it and 'lock-superuser' role is the role for the other one to unlock content

JCR function APIs:

• javax.jcr.lock.LockManager.lock
• javax.jcr.lock.LockManager.unlock

*This feature is conflicted with our declared function in https://wiki.magnolia-cms.com/display/SERVICES/Hard+Locking+submodule*

Hard Locking nodes ensures that only the user who locked the node is able to make changes to it until it is unlocked again.