etianen / etianen/django-python3-ldap

ldap3.ServerPool usage appears to be hardcoded

Open
#279 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
428
Forks
122
PR merge metrics
No merged PRs in 30d

Description

It's impossible to use this library without the ldap3.ServerPool functionality because it appears to be hardcoded into here.

I get `raise LDAPServerPoolError('pools can be exhausted only when checking for active servers')` but that's after I set `LDAP_AUTH_POOL_ACTIVE = False`.

I was definitely not expecting it to completely crash when changing a boolean default value like this. Is this an oversight or am I missing something obvious?

I'm using version 0.15.8

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.