mirror of
https://github.com/BookStackApp/BookStack.git
synced 2026-02-06 00:59:39 +03:00
Auth driver [ldap-session] for guard [ldap] is not defined #5207
Reference in New Issue
Block a user
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?
Originally created by @513ry on GitHub (Mar 4, 2025).
Describe the Bug
When using
Illuminate\Support\Facades\Auth::user()I get following error:Cleaning catch and configuration with artisan does not work as it return the same error.
LDAP works otherwise for login and other BookStack features.
Steps to Reproduce
Illuminate\Support\Facades\Auth::user()inside functions.php of that themeExpected Behaviour
Get current user to filter database query.
Screenshots or Additional Context
No response
Browser Details
No response
Exact BookStack Version
v24.05.4
@ssddanbrown commented on GitHub (Mar 4, 2025):
Hi @513ry,
This could occur if attempting to get the user before the AuthServiceProvider has booted.
This could occur in your theme if you're attempting to get the user in the app_boot event (or within the global top-level space of the functions.php file).
Should work though if you're attempting to the the user within any other theme event.
If you think these is an issue, feel free to provide an example
functions.phpfile which can be used to replicate the issue.@513ry commented on GitHub (Mar 4, 2025):
Thank you for your answer @ssddanbrown.
I moved the
Auth::user()call after route callback (Route::get) and LDAP seems okay now. AlthoughAuth::user()have returnednull. Similar thesession::all()array is empty. Should I verify the user inside another event?@ssddanbrown commented on GitHub (Mar 4, 2025):
@513ry It depends on what you're attempting to do. It comes down to timing since some things can run before the auth/session has performed its own setup.
All of the main theme events provided, aside from APP_BOOT (and maybe WEB_MIDDLEWARE_BEFORE?), should be after any active user/auth session handling is done, so calls to the user within callback of those should work be fine.
BTW, there is a global
user()helper function which is what I mostly use in-app:13dae24cbe/app/App/helpers.php (L33-L40)This will default to the guest user, where not logged in, which can be handy in many cases.
@ssddanbrown commented on GitHub (Mar 4, 2025):
Also, if you're adding custom routes at the top level, you might not have the required session/auth middlware active.
We expose the
ROUTES_REGISTER_WEBandROUTES_REGISTER_WEB_AUTHto make registering routes easier for a normal web context (with active sessions and middlware).An example can be seen here:
https://www.bookstackapp.com/blog/bookstack-release-v23-12/#logical-theme-system-events-to-register-routes
@513ry commented on GitHub (Mar 4, 2025):
I been not adding the route at the top level, I used the
APP::BOOTevent. Thanks, that is a much better approach!@513ry commented on GitHub (Mar 4, 2025):
Do you have maybe an example of how filtering a queue by user id is generally done?
@ssddanbrown commented on GitHub (Mar 4, 2025):
I'm not sure what you mean by that, what queue is that specifically referring to?
@513ry commented on GitHub (Mar 5, 2025):
Sorry, I meant database "query". From my understanding
scopes('visible')does only return the public properties of anEntity. Right?@513ry commented on GitHub (Mar 5, 2025):
Well, this is out of the initial subject of this issue.
PermissionApplicatorwas what I been looking for (more specific restrictEntityQuery).