[
https://jira.codehaus.org/browse/MRM-1709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Lamy updated MRM-1709:
------------------------------
Fix Version/s: 1.4-M4
Assignee: Olivier Lamy
> Default redback admin does not work anymore when using LDAP in the new UI
> -------------------------------------------------------------------------
>
> Key: MRM-1709
> URL: https://jira.codehaus.org/browse/MRM-1709
> Project: Archiva
> Issue Type: Bug
> Components: Users/Security
> Affects Versions: 1.4-M3
> Reporter: Maria Odea Ching
> Assignee: Olivier Lamy
> Fix For: 1.4-M4
>
>
> Previously, the config @redback.default.admin@ in security.properties file is
> used upon initial startup on a clean installation of Archiva with LDAP.
> In the new UI, you'd be prompted to create an admin account even if the
> property has been set to an existing LDAP user. But when you create an admin
> account, it doesn't get persisted since it is configured to use LDAP so you
> won't be able to do anything at all.
> Workaround for this problem is to:
> # Start Archiva without LDAP configured
> # Create an admin account then create another account whose username exists
> in LDAP (ex. oching) then assign that account with the System Admin role.
> # Shutdown Archiva then configure it to use LDAP
> # Start Archiva
> # Login as the second user you created (in our case, as oching). You should
> be able to do admin tasks.
--
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
