Rudder

Is the switch to beta2 meaning it's gonna be ready for 2.10 ?

The switch was an automated update due to the closing of beta1.

I looked to that one, but Spring is... well. Such a mess, that's just awful. So, in short, I have to spend more time on it, and for now, I'm not sure about how to solve that. Not that's not possible. Just I have to find the good incantation to summon the good will of Spring.

So, I fear that it won't go into 2.10.0, sorry.

François those options are exactly what's needed

For the properties documentation, we should add two example, one really LDAP, one AD oriented.

Do not use that:
- rudder.auth.ldap.connection.user.dn=cn=admin,dc=mycorp,dc=com
- rudder.auth.ldap.connection.user.password=secret

But that:
- rudder.auth.ldap.connection.bind.dn=cn=admin,dc=mycorp,dc=com
- rudder.auth.ldap.connection.bind.password=secret

LDAP example:
- rudder.auth.ldap.searchbase=ou=People
- rudder.auth.ldap.filter=(&(uid={0})(objectclass=person))

AD example
- rudder.auth.ldap.searchbase=
- rudder.auth.ldap.filter=(&(sAMAccountName={0})(objectclass=user))

Plus, in comment say that the method used is bind/search/rebind.

Plus, update the documentation to remove the hack about editing XML files and add the LDAP section along with the authentication like that:

- 8.7 Password upgrade + 10.4 password management (minus the LDAP sub-section) => 8.7 Internal Password Management
- 10.3 User Management + a new LDAP section => 8.6 User Management

Applied in changeset 0ec0da5cdb755569a153e961c01af0a80a6efd0e.