Some internal users authenticating against our LDAP (new hires that have never logged into rhodecode before) are reporting symptoms that they're unable to login. However, it seems that they're authenticating properly against LDAP, but their RhodeCode account is promptly set 'inactive' and RhodeCode will not associate the user with their session.
This started happening after upgrading from 1.6.5 to 1.7.1.
Any ideas? I've manually reset their account to active, however, this will be an ongoing problem I think (I definitely did NOT set their account inactive).