[
https://issues.apache.org/jira/browse/JCRVLT-515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17348077#comment-17348077
]
Konrad Windszus commented on JCRVLT-515:
----------------------------------------
The additional attribute exposed since OAK-9415 is evaluated in
https://github.com/apache/jackrabbit-filevault/commit/78a225aa1ef3167ef78e17b44346f317f65617c3
now as well. This requires running with Oak 1.40+ though.
> AdminPermissionChecker should evaluate all principals bound to the Session
> --------------------------------------------------------------------------
>
> Key: JCRVLT-515
> URL: https://issues.apache.org/jira/browse/JCRVLT-515
> Project: Jackrabbit FileVault
> Issue Type: Improvement
> Components: vlt
> Reporter: Konrad Windszus
> Assignee: Konrad Windszus
> Priority: Major
> Fix For: 3.4.12
>
>
> Currently the AdminPermissionChecker only evaluates the session-bound user id
> in
> https://github.com/kwin/jackrabbit-filevault/blob/49e3c2179c18e0552e49b0671843d85d045ebf48/vault-core/src/main/java/org/apache/jackrabbit/vault/packaging/impl/AdminPermissionChecker.java#L54.
> This does not work well with principal based login (like with Sling Service
> Authentication) as in general only the first principal is returned (in case
> it is backed by a real JCR user). Instead one should leverage
> {{org.apache.jackrabbit.api.security.principal.PrincipalManager}} to retrieve
> all principals bound to the session and check that at least one is the
> administrator.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
