You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "angela (JIRA)" <ji...@apache.org> on 2016/06/10 13:00:23 UTC
[jira] [Created] (OAK-4462) LoginModuleImpl: option to have
AuthInfo populated with userId instead of loginName
angela created OAK-4462:
---------------------------
Summary: LoginModuleImpl: option to have AuthInfo populated with userId instead of loginName
Key: OAK-4462
URL: https://issues.apache.org/jira/browse/OAK-4462
Project: Jackrabbit Oak
Issue Type: Improvement
Components: core
Reporter: angela
Assignee: angela
Priority: Minor
The current implementation of {{LoginModuleImpl}} _always_ populates the {{AuthInfo}} with the userId as extracted from the {{Credentials}} or the shared state; doing so will make {{Session.getUserID()}} expose the 'login-id', which may or may not correspond to the ID of the corresponding {{User}} as it is expected to exist with this login module implementation.
While this clearly is a design decision with the {{LoginModuleImpl}} and perfectly in accordance with the API contract of {{Session.getUserID()}}, there might be cases, where equality of {{Session.getUserID()}} and {{User.getID()}} would be desirable.
So, we may think about adding an option to the default authentication; be it with {{LoginModuleImpl}} and|or the {{UserAuthenticationFactory}}|{{UserAuthentication}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)