[ 
https://issues.apache.org/jira/browse/OAK-9415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17329243#comment-17329243
 ] 

Angela Schreiber edited comment on OAK-9415 at 4/22/21, 4:16 PM:
-----------------------------------------------------------------

[~kwin], as pointed on oak-dev this could be achieved through session 
attributes, which doesn't require any API changes. if a given implementation 
cannot or doesn't want to expose the principals as attribute it would just 
return null for the attribute value and not expose the attribute-name. 
note: i would definitely prefer that over adding a new method to 
JackrabbitSession.


was (Author: anchela):
[~kwin], as pointed on oak-dev this could be achieved through session 
attributes, which doesn't require any API changes. if a given implementation 
cannot or doesn't want to expose the principals as attribute it would just 
return null for the attribute value and not expose the attribute-name. 

> Extend JackrabbitSession to allow access to all principals bound to the 
> current session
> ---------------------------------------------------------------------------------------
>
>                 Key: OAK-9415
>                 URL: https://issues.apache.org/jira/browse/OAK-9415
>             Project: Jackrabbit Oak
>          Issue Type: New Feature
>          Components: jackrabbit-api
>            Reporter: Konrad Windszus
>            Assignee: Konrad Windszus
>            Priority: Major
>
> Currently there is no API to retrieve all principals bound to a specific 
> session (see https://issues.apache.org/jira/browse/JCRVLT-515). 
> {{Session.getUserId()}} may at most return the user backing the first 
> principal and 
> https://www.javadoc.io/doc/org.apache.jackrabbit/jackrabbit-api/latest/org/apache/jackrabbit/api/JackrabbitSession.html
>  does not expose any other method which can be used for that.
> In Oak this can be simply implemented via 
> {{ContentSession.getAuthInfo().getPrincipals()}} 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to