[
https://issues.apache.org/jira/browse/SLING-11723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus updated SLING-11723:
------------------------------------
Description:
Currently ResourceResolver only exposes the {{getUserID()}} for debugging
purposes. 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).
was:
Currently ResourceResolver only exposes the {{getUserID()}} for debugging
purposes. 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)
> 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
> purposes. 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)
