Make sure you have configured an admin user that exists in LDAP - at the moment there's no way to use an internal user for that.
Here is a configuration template I use which should show the values you'd need to populate: https://github.com/maestrodev/puppet-archiva/blob/master/templates/security.properties.erb On 12/11/2011, at 11:21 PM, sam-the-man wrote: > > I'm coming to the end of a long, drawn-out server setup. > > Archiva is the last piece of the puzzle. The kicker - I need to get it to > authenticate and authorize using ldap. > > I know my LDAP server is working fine. Archiva is (was?) working fine too. > > So I install archiva and load it for the first time. It forces me to create > an admin. Then I'm in, it works, etc. > > So I add all the LDAP configuration options to the security.properties file, > and then restart archiva. > > When the LDAP stuff is in the security.properties file, and I try to access > archiva, it goes back to the create admin field no MATTER what I do, or what > I click. I already created an admin, so why is it trying to force me to make > another after I add the LDAP stuff? Configuration files coming... > > > -- > View this message in context: > http://old.nabble.com/Weird-problems-with-LDAP-integration-tp32834029p32834029.html > Sent from the archiva-users mailing list archive at Nabble.com. > -- Brett Porter [email protected] http://brettporter.wordpress.com/
