Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
1.4-M3
-
None
Description
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.