You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org> on 2018/02/05 09:40:00 UTC

[jira] [Updated] (KARAF-4496) UserPrincipal lookup in the JAAS' BackingEngine

     [ https://issues.apache.org/jira/browse/KARAF-4496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jean-Baptiste Onofré updated KARAF-4496:
----------------------------------------
    Component/s: karaf-security

> UserPrincipal lookup in the JAAS' BackingEngine
> -----------------------------------------------
>
>                 Key: KARAF-4496
>                 URL: https://issues.apache.org/jira/browse/KARAF-4496
>             Project: Karaf
>          Issue Type: Improvement
>          Components: karaf-security
>            Reporter: Yurii Rashkovskii
>            Assignee: Jean-Baptiste Onofré
>            Priority: Minor
>              Labels: jaas
>             Fix For: 4.2.0, 4.1.5
>
>
> I have a suggestion for improving org.apache.karaf.jaas.modules.BackingEngine
> Currently, the only way to lookup an individual user (as far as I can tell) is to iterate through the result of BackingEngine#listUsers() and find the required user. This is fine if the number of users is reasonably low. However, when JAAS infrastructure is used for public systems (say, a SaaS), it quickly becomes a bottleneck.
> I suggest adding something like `public UserPrincipal lookupUser(String name)` to avoid this problem (also, it should return `null` if no such user found , or throw an exception)
> I am happy to contribute a PR promptly if this change will be approved.
> Thoughts?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)