mirror of
https://github.com/BookStackApp/BookStack.git
synced 2026-02-05 00:29:48 +03:00
External Authentication ID stopped working #1765
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 @kabaga on GitHub (Jun 14, 2020).
Describe the bug
When LDAP has been enabled, LDAP users are able to login. However, the local admin account with External Authentication ID configured, cannot login.
Steps To Reproduce
Steps to reproduce the behavior:
Expected behavior
Step 3 should allow the local admin account to login to the system.
Screenshots
n/a
Your Configuration (please complete the following information):
Additional context
n/a
@ssddanbrown commented on GitHub (Jun 21, 2020):
Hi @kabaga,
Just so I understand, On step 2 where you mention a "local admin account", is this an account that exists in your LDAP system?
@kabaga commented on GitHub (Jun 21, 2020):
No, the admin account locally created in Bookstack
@Dayflare commented on GitHub (Jun 26, 2020):
to login with the standard bookstack authentication system you need to change AUTH_METHOD=standard
if you set it to ldap it always tries to authenticate with the ldap server.
@kabaga commented on GitHub (Jun 27, 2020):
I should be able to use the local account because it has admin privilege. To get the local account to work with ldap, the External Authentication ID should be enabled. https://www.bookstackapp.com/docs/admin/ldap-auth/
@ssddanbrown commented on GitHub (Jun 28, 2020):
Hi @kabaga,
Since you're getting ""These credentials do not match our records." I'd imagine one of the following is true:
Does LDAP login work for other LDAP accounts?
If so, and it's only this admin account you're having issues with, You could try removing any common details, with the LDAP user, from the BookStack admin user, including clearing the "External Auth ID". Then, with LDAP enabled, login as the intended LDAP account to create the account with the right settings, then log back in with
standardauthentication to promote that new "admin" LDAP user.@kabaga commented on GitHub (Jul 13, 2020):
Hi,
Sorry for the late reply. In the Bookstack settings, I was using the email login when it was failing. Everything seems to be working as intended. The problem is more of a user error.
Thanks!