Allow using Django-local accounts in addition to LDAP accounts #389

Closed
opened 2021-02-25 23:26:46 +01:00 by nik · 4 comments
Owner

Currently, LDAP is checked first on authentication, and if no matching user is found in LDAP, authentication fails. This ensures that if users are removed from an LDAP directory, they immediately are blocked from AlekSIS as well.

We should evaluate allowing login for Django users as well, but we need to make sure it only works for users that were never synced from LDAP.

Currently, LDAP is checked first on authentication, and if no matching user is found in LDAP, authentication fails. This ensures that if users are removed from an LDAP directory, they immediately are blocked from AlekSIS as well. We should evaluate allowing login for Django users as well, but we need to make sure it only works for users that were never synced from LDAP.
Author
Owner

mentioned in issue #388

mentioned in issue #388
Author
Owner

created merge request !2146 to address this issue

created merge request !2146 to address this issue
Author
Owner

mentioned in merge request !2146

mentioned in merge request !2146
Owner

mentioned in commit 72bcb568be

mentioned in commit 72bcb568be6a1226c1498f8cfaaf01c122f4579f
Sign in to join this conversation.
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
aleksis/AlekSIS-Core#389
No description provided.