[
https://issues.apache.org/jira/browse/SLING-7668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu resolved SLING-7668.
------------------------------------
Resolution: Fixed
Follow-up fix applied in [commit
7b3e0a|https://github.com/apache/sling-org-apache-sling-jcr-jackrabbit-usermanager/pull/2/commits/7b3e0a1d997421ab39e315f36d646160ee47897b]
> Add adapterFactory to obtain Authorizable or User from ResourceResolver
> -----------------------------------------------------------------------
>
> Key: SLING-7668
> URL: https://issues.apache.org/jira/browse/SLING-7668
> Project: Sling
> Issue Type: Improvement
> Components: JCR
> Reporter: Dominik Süß
> Assignee: Robert Munteanu
> Priority: Major
> Fix For: JCR Jackrabbit User Manager 2.2.8
>
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> The process to extract the current user from a resourceResolver is currently
> not obvious in a plain Sling setup (AEM as commercial product has a
> propietary usermanager providing corresponding functionality) so this ticket
> is about adding a corresponding adapterFactory to the sling jackrabbit
> usermanager to hide away the necessary boilerplate code.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
