[
https://issues.apache.org/jira/browse/OAK-5903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela updated OAK-5903:
------------------------
Attachment: LoginLogoutTest-authenticationWithPrincipal-iterations1.txt
LoginLogoutTest-statusquo-iterations1.txt
LoginLogout_token_statusquo.txt
LoginLogout_token_authenticationWithPrincipal.txt
LoginLogout_authenticationWithPrincipal.txt
LoginLogout_statusquo_170.txt
attached result for {{LoginLogoutTest}} benchmark.
- _*statusquo_: test run on oak-trunk without modifications
- _*authenticationWithPrincipal_: test run with the extension in place
the following test-setup scenarios were tested:
- default setup
- setup including subsequent token-login
- default setup with number of iterations set to 1
> 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
> 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)
