You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@archiva.apache.org by "Olivier Lamy (JIRA)" <ji...@codehaus.org> on 2012/12/08 16:55:13 UTC

[jira] (MRM-1721) Chaining user manager

     [ https://jira.codehaus.org/browse/MRM-1721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Olivier Lamy updated MRM-1721:
------------------------------

    Assignee: Olivier Lamy
     Summary: Chaining user manager  (was: Have database user-auth as fallback for LDAP)
    
> Chaining user manager
> ---------------------
>
>                 Key: MRM-1721
>                 URL: https://jira.codehaus.org/browse/MRM-1721
>             Project: Archiva
>          Issue Type: Improvement
>          Components: Users/Security
>    Affects Versions: 1.4-M3
>            Reporter: Sascha Vogt
>            Assignee: Olivier Lamy
>            Priority: Minor
>             Fix For: 1.4-M4
>
>
> It would be really helpful to have a "chain" of authentication modules, where if the first one fails a second one is queried.
> The main use-case here is if one has LDAP user auth configured (typical corporate environment), but also needs a few technical users (like a Jenkins instance) which are not in the corporate LDAP. 
> A side benefit for that is, that one can hard-code a "backup-administrator" which can be used, if one accidentally breaks the LDAP configuration or if the LDAP isn't available at all.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira