CE: LDAPS authentication fails

Support
1

Hi all,
dunno if this is the right place to report bugs… I’ll try.

Just installed Community Edition 4.0.1
Configured LDAP authentication.

I get the following traceback after an auth try:

2016-06-08 13:40:51.752 INFO  [rhodecode.authentication.base] Authenticating user `my.username` using egg:rhodecode-enterprise-ce#ldap plugin
2016-06-08 13:40:51.753 ERROR [rhodecode.authentication.plugins.auth_ldap] Other exception
Traceback (most recent call last):
  File "/opt/rhodecode/store/7xack0znza8fdx0wvdsz3sn9pwh9sz7p-python2.7-rhodecode-enterprise-ce-4.0.1/lib/python2.7/site-packages/rhodecode/authentication/plugins/auth_ldap.py", line 406, in auth
    aldap = AuthLdap(**ldap_args)
  File "/opt/rhodecode/store/7xack0znza8fdx0wvdsz3sn9pwh9sz7p-python2.7-rhodecode-enterprise-ce-4.0.1/lib/python2.7/site-packages/rhodecode/authentication/plugins/auth_ldap.py", line 174, in __init__
    if isinstance(ldap, Missing):
TypeError: isinstance() arg 2 must be a class, type, or tuple of classes and types
2016-06-08 13:40:51.756 WARNI [rhodecode.model.validators] user my.username failed to authenticate
2016-06-08 13:40:51.875 INFO  [rhodecode.lib.middleware.request_wrapper] IP: 192.167.60.131 Request to /_admin/login time: 0.210s

any hint?

thanks,
alessandro.

2

Hi Alessandro,

Thanks for reporting this. We’re working on a fix it will be available in next 1-2 days.

1 Like
3

I had the same problem. I did a temporary workaround:

In “/opt/rhodecode/store/7xack0znza8fdx0wvdsz3sn9pwh9sz7p-python2.7-rhodecode-enterprise-ce-4.0.1/lib/python2.7/site-packages/rhodecode/authentication/plugins/auth_ldap.py”, comment out line 174 and 175
#if isinstance(ldap, Missing): # raise LdapImportError("Missing or incompatible ldap library")

After restarting my instance (rccontrol restart community-1), LDAP was working.

Looking forward to a more permanent fix.

1 Like
4

Also hitting the same issue. For some reason, the workaround suggested above does not seem to do the trick.

Glad to hear you guys are already working on the fix!

5

Hi,

actually release 4.1 is out already, feel free to update the issue should be fixed ! Sorry for the troubles guys.

Best,

6

Works like a charm… thank you for the amazingly fast response!!