Sajeyks 0cb0344ac8 Compute the next uidNumber from LDAP instead of a local file ... The highest uidNumber was cached in dal/ldap_max_uid_file. That breaks with more than one replica and is lost on every container restart. The uniqueness check behind it searched base '' (the root DSE), which OpenLDAP never matches, so nothing caught a stale file. The error path also referenced a setting that does not exist. Now a paged search over ENTIRE_SEARCH_BASE finds the highest uidNumber on each activation. Numbering is unchanged: the next number is above both LDAP_DEFAULT_START_UID and every existing uidNumber. LDAP_MAX_UID_FILE_PATH is no longer used.		2026-11-06 15:03:57 +03:00
..
migrations	Keep passwords out of activation links	2026-11-06 15:02:41 +03:00
static	added red btn similar to blue one	2019-04-16 11:52:22 -04:00
templates	Register add	2021-12-12 20:39:32 +01:00
tests	Compute the next uidNumber from LDAP instead of a local file	2026-11-06 15:03:57 +03:00
__init__.py	Move project files to root directory	2019-02-17 17:43:06 +01:00
env.sample	Populate README, refresh configuration template	2020-05-01 11:07:29 +02:00
forms.py	Ask for username instead of email for login, validate username on	2020-05-01 11:08:13 +02:00
models.py	Keep passwords out of activation links	2026-11-06 15:02:41 +03:00
settings.py	Compute the next uidNumber from LDAP instead of a local file	2026-11-06 15:03:57 +03:00
ungleich_ldap.py	Compute the next uidNumber from LDAP instead of a local file	2026-11-06 15:03:57 +03:00
urls.py	Keep passwords out of activation links	2026-11-06 15:02:41 +03:00
views.py	Reject usernames that exist anywhere in the directory	2026-11-06 15:03:14 +03:00
wsgi.py	Move project files to root directory	2019-02-17 17:43:06 +01:00