Local Admin account does not work with LDAP (commit 519283e) #3343

New Issue

OVERLORD · 2026-02-05T06:25:03+03:00

OVERLORD commented

2026-02-05 06:25:03 +03:00

Originally created by @Sys-Monitor on GitHub (Nov 14, 2022).

Attempted Debugging

I have read the debugging page

Searched GitHub Issues

I have searched GitHub for the issue.

Describe the Scenario

According to the following commit, an admin account should be validated across all login types:
519283e643

This does not seem to be the case as the local admin account "Admin" that was setup at the start does not work when enabling LDAP. It only works when disabling LDAP.

(I've also tried the associated e-mail and that does not work either)

Exact BookStack Version

22.10.2

Log Content

Nothing is logged into laravel.log or apache2/error.log. APP_DEBUG=true doesn't show anything different. Still only throws the same error on screen.

PHP Version

8.1.2

Hosting Environment

Ubuntu 22.04.1 LTS, installed using installation script

Originally created by @Sys-Monitor on GitHub (Nov 14, 2022). ### Attempted Debugging - [X] I have read the debugging page ### Searched GitHub Issues - [X] I have searched GitHub for the issue. ### Describe the Scenario According to the following commit, an admin account should be validated across all login types: https://github.com/BookStackApp/BookStack/commit/519283e643f9697952d49c7009dd9e9745cb4319 This does not seem to be the case as the local admin account "Admin" that was setup at the start does not work when enabling LDAP. It **only** works when disabling LDAP. ![image](https://user-images.githubusercontent.com/106233546/201640830-35b77b21-5df5-42f7-94c3-8e8baad87baa.png) (I've also tried the associated e-mail and that does not work either) ### Exact BookStack Version 22.10.2 ### Log Content Nothing is logged into laravel.log or apache2/error.log. APP_DEBUG=true doesn't show anything different. Still only throws the same error on screen. ### PHP Version 8.1.2 ### Hosting Environment Ubuntu 22.04.1 LTS, installed using installation script

OVERLORD added the 🐕 Support label 2026-02-05 06:25:03 +03:00

OVERLORD closed this issue

2026-02-05 06:25:09 +03:00

OVERLORD commented

2026-02-05 06:25:12 +03:00

@ssddanbrown commented on GitHub (Nov 14, 2022):

That referenced commit is regarding how the back-end auth session is managed. The user-visible login forms, and their subsequent login actions, are still different between the auth options.

If attempting to login again with the original admin account, via non-LDAP, you'll need to switch the AUTH_METHOD back to standard (Or comment it out with a #) before refreshing the login page to show the normal auth form.

@ssddanbrown commented on GitHub (Nov 14, 2022): That referenced commit is regarding how the back-end auth session is managed. The user-visible login forms, and their subsequent login actions, are still different between the auth options. If attempting to login again with the original admin account, via non-LDAP, you'll need to switch the `AUTH_METHOD` back to `standard` (Or comment it out with a `#`) before refreshing the login page to show the normal auth form.

OVERLORD commented

2026-02-05 06:25:14 +03:00

@Sys-Monitor commented on GitHub (Nov 14, 2022):

I see. I thought we'd be able to manage the instance in case the AD connection goes down without having to edit the server config. I'll close the issue then.

@Sys-Monitor commented on GitHub (Nov 14, 2022): I see. I thought we'd be able to manage the instance in case the AD connection goes down without having to edit the server config. I'll close the issue then.

OVERLORD referenced this issue

2026-02-05 09:53:45 +03:00

API: Add system endpoint to provide app version number amoung other details #5277

Sign in to join this conversation.