Seems like its a single PHP process?

It can be sourced back to the same cause, but the outcome is differnet.

Describe the Bug

When a user log in, the whole Bookstack instance does not respond anymore. The page doesnt load and no actions can be done.
The login takes about 10-20 (even 30 ) seconds and in that time nobody is able to work in Bookstack.
Using a reverse proxy you get a timeout at some point (yes, I know you can increase the limit, but this does not solve the problem)

One the login finishes, the instance works snappy again.

I already submitted a feature request, which would solve this issue: #6128

Steps to Reproduce

1. Have a big AD / LDAP environment
2. Activate LDAP Login and Group Sync
3. Specify "External Authentication IDs" in roles to match LDAP groups
4. User (who is part of the groups) tries to log in

Expected Behaviour

Snappy login

Screenshots or Additional Context

No response

Browser Details

Edge 148.0.3967.54 (Official Build) (64-Bit) on Windows 11

Exact BookStack Version

v26.03.3

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:

1. 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.

2. 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)))

3. "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=main

Describe 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?

• I have searched for existing issues and none cover my fundamental request

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?

• This request only contains the thoughts & ideas of a human

I'm having the same issue.