[
https://issues.apache.org/jira/browse/SLING-11723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17646528#comment-17646528
]
Angela Schreiber commented on SLING-11723:
------------------------------------------
for the JCR specific pieces i believe it should be possible to adapt the
resource resolver to a jcr session and use the bound principals attribute that
you have added lately (see
https://github.com/apache/jackrabbit-oak/blob/trunk/oak-jcr/src/main/java/org/apache/jackrabbit/oak/jcr/session/SessionImpl.java#L287-L289).
> Expose more authentication information from ResourceResolver
> ------------------------------------------------------------
>
> Key: SLING-11723
> URL: https://issues.apache.org/jira/browse/SLING-11723
> Project: Sling
> Issue Type: Improvement
> Components: API
> Reporter: Konrad Windszus
> Priority: Major
>
> Currently ResourceResolver only exposes the {{getUserID()}} for debugging
> authorization related issues. With the addition of SLING-6963 it would be
> helpful to additionally expose:
> - if a resource resolver is a service resource resolver (applies to all
> providers)
> - if it is based on principal names or regular authorizable ids (JCR provider
> specific, although the configuration format is agnostic)
> This information is crucial to figure out why a particular resource cannot be
> resolved (due to missing permissions).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
