[
https://issues.apache.org/jira/browse/OAK-5903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela resolved OAK-5903.
-------------------------
Resolution: Fixed
Fix Version/s: 1.8
1.7.0
Committed revision 1785855.
> Authentication: add extension to retrieve user principal
> --------------------------------------------------------
>
> Key: OAK-5903
> URL: https://issues.apache.org/jira/browse/OAK-5903
> Project: Jackrabbit Oak
> Issue Type: New Feature
> Components: core
> Reporter: angela
> Assignee: angela
> Labels: performance
> Fix For: 1.7.0, 1.8
>
> Attachments: LoginLogout_authenticationWithPrincipal.txt,
> LoginLogout_statusquo_170.txt,
> LoginLogoutTest-authenticationWithPrincipal-iterations1.txt,
> LoginLogoutTest-statusquo-iterations1.txt,
> LoginLogout_token_authenticationWithPrincipal.txt,
> LoginLogout_token_statusquo.txt
>
>
> In the current default setup the implementations of the {{Authentication}}
> interface resolve a user for the given login credentials but don't provide
> means to retrieve the associated principal. Consequently upon
> {{LoginModule.commit}} the user needs to resolved a second time to compute
> the set of all principals. This could be simplified by using
> {{PrincipalProvider.getGroupMembership(Principal)}} if the users principals
> was available upon successful call to {{Authentication.authenticate}}.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
