[SLING-7613] Remove deprecation of SlingRepository.loginAdministrative()

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: JCR API 2.4.0
• Component/s: API
• Assignee: Robert Munteanu
• Reporter: Joerg Hoh
• Created: 24/Apr/18 07:36
• Updated: 11/Feb/22 17:26
• Resolved: 30/Jul/18 15:20

Description

There was a discussion on the Sling user list [1] about usecases which can only be solved using the deprecated loginAdministrative() call. In the context of Sling and Oak there are indeed a few cases which can be solved best with a true admin session:

• locking and unlocking nodes which have been locked by a different user.
• at deployments resources/nodes are deployed at many locations inside the repo, so you can either use an admin session or a system-user with an equivalent set of permissions.
• the discussions leaves it open if the impersonation feature internally relies on an admin session or can be achieved without it.

System users should be the preferred, but I would like to have an offical and non-deprecated way to get an admin session in the API. It's ok if I need to configure the explicit whitelisting as it is in place right now. But it should be there.
Plus there should be proper documentation when to use which approach.

[1] http://apache-sling.73963.n3.nabble.com/Deprecation-of-SlingRepository-loginAdministrative-td4081024.html

Issue Links

• links to: GitHub Pull Request #1