Closed strangeman closed 6 years ago
Hello, any update on this?
Sorry, I have not had a chance to dig into this. However, I have a container running Sentry Server 8.20.0 with django-auth-ldap 1.2.16, and I am unable to reproduce the problem.
@rakshazi as another workaround you may restrict an django-auth-ldap version in sentry's requirements.txt:
cat /opt/sentry/build/requirements.txt
# Add plugins here
sentry-ldap-auth
django-auth-ldap <=1.2.13,>=1.2.5
@barronhagerman maybe it related to the LDAP server implementation, I still able to reproduce the problem with Sentry Server 8.20.0 and django-auth-ldap 1.2.16. We use Crowd SSO with LDAP bindings for it.
Here is my solution for this problem: https://github.com/getsentry/sentry/issues/6609#issuecomment-346674096
Yeah, still an issue. Edit: solved with a version pin like @rakshazi
I have pinned the version of django-auth-ldap to 1.2.* because there is a problem installing sentry-ldap-auth with django-auth-ldap 1.3. However, everything seems to work fine for me with django-auth-ldap 1.2.16.
How to reproduce:
Expected result
Actual result
Logs
First, successful login:
Second, unsucsessful login:
This behavior exists with
django-auth-ldap 1.2.14, 1.2.15, 1.2.16
. I think this is related toUnder search/bind mode, the user's DN will now be cached for performance
(https://bitbucket.org/psagers/django-auth-ldap/src/569b6ca46ce8a27af2b6d712caea09b2ed6c894e/CHANGES?at=default&fileviewer=file-view-default#CHANGES-41).As a workaround, I suggest to pin django-auth-ldap requirement.