More LDAP Options #6128
Labels
No labels
Focus: A11y
Focus: Admin/Meta
Focus: Authentication
Focus: Back-End
Focus: Database
Focus: Design & UX
Focus: Editor - Markdown
Focus: Editor - WYSIWYG
Focus: Export System
Focus: Front-End
Focus: Translations
Focus: View Customization
Is: Docs Update
Is: Enhancement
Is: Priority
Is: Security
Is: Upstream
Status
Blocked
Status
Open to discussion
Status
Out of scope
Status
Pending Validation
Type
API Request
Type
Bug Report
Type
Feature Request
Type
Happy feedback
Type
Maintenance
Type
Question
Type
Support
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
bookstack/bookstack#6128
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Describe the feature you'd like
Right now, every login in our environment needs 10-20 seconds, even causes timeouts. And while a user tries to log in, the whole bookstack instance freezes and is not usable for every user! Once the user successfully logged in, the instance is snappy again.
Currently its caused by the LDAP group sync which tries to fetch every LDAP group (I think)
It would help to specify LDAP Scopes for this:
LDAP Filter to limit the search scope for groups:
This can be achieved by a plain LDAP query or by specifying a specific OU / container which has all needed groups in it.
LDAP Filter for users
This can also be achieved by a plain LDAP query. In our case we would like to limit the users that are able to log in by requiring a specific group membership
Example:
(&(|(memberOf=cn=fancygroup,ou=bookstack,o=main))(|(objectClass=Person)(objectClass=inetOrgPerson)))"External Authentication IDs": Specify DN instead of CN (both for user and group/role)
This eliminates searching the whole tree for a CN and instead directly addresses the DN. (which is the full LDAP path)
This also elimiates problems witn CN duplicate names.
Example:
cn=fancygroup,ou=bookstack,o=mainDescribe the benefits this would bring to existing BookStack users
Users in large AD / LDAP environments would get a massive performance gain with logins and there would no impact if another user tries to log in.
Can the goal of this request already be achieved via other means?
No
Have you searched for an existing open/closed issue?
How long have you been using BookStack?
Under 3 months
Additional context
No response
Have you used generative AI/LLMs to create any thoughts in this request?