mirror of
https://github.com/BookStackApp/BookStack.git
synced 2026-05-04 18:08:46 +03:00
LDAP auth not working #2808
Closed
opened 2026-02-05 05:15:41 +03:00 by OVERLORD
·
5 comments
No Branch/Tag Specified
development
l10n_development
release
v26-03
ci_fixing
codeberg-actions
lexical_may_2026
MilnerMart/development
sort_rule_text
GamerClassN7/impersonations-for-admin
Zhey-on/feature/csp-image-css-controls-6033
tortillas5/development
clauvaldez/mfaReset
llm_only
vectors
McTom234/oidc-key-algorithms
docker_env
drawio_rendering
user_permissions
ldap_host_failover
svg_image
prosemirror
captcha_example
fix/video-export
v26.03.4
v26.03.3
v26.03.2
v26.03.1
v26.03
v25.12.9
v25.12.8
v25.12.7
v25.12.6
v25.12.5
v25.12.4
v25.12.3
v25.12.2
v25.12.1
v25.12
v25.11.6
v25.11.5
v25.11.4
v24.11.4
v25.11.3
v25.11.2
v25.11.1
v25.11
v25.07.3
v25.07.2
v25.07.1
v25.07
v25.05.2
v25.05.1
v25.05
v25.02.5
v25.02.4
v25.02.3
v25.02.2
v25.02.1
v25.02
v24.12.1
v24.12
v24.10.3
v24.10.2
v24.10.1
v24.10
v24.05.4
v24.05.3
v24.05.2
v24.05.1
v24.05
v24.02.3
v24.02.2
v24.02.1
v24.02
v23.12.3
v23.12.2
v23.12.1
v23.12
v23.10.4
v23.10.3
v23.10.2
v23.10.1
v23.10
v23.08.3
v23.08.2
v23.08.1
v23.08
v23.06.2
v23.06.1
v23.06
v23.05.2
v23.05.1
v23.05
v23.02.3
v23.02.2
v23.02.1
v23.02
v23.01.1
v23.01
v22.11.1
v22.11
v22.10.2
v22.10.1
v22.10
v22.09.1
v22.09
v22.07.3
v22.07.2
v22.07.1
v22.07
v22.06.2
v22.06.1
v22.06
v22.04.2
v22.04.1
v22.04
v22.03.1
v22.03
v22.02.3
v22.02.2
v22.02.1
v22.02
v21.12.5
v21.12.4
v21.12.3
v21.12.2
v21.12.1
v21.12
v21.11.3
v21.11.2
v21.11.1
v21.11
v21.10.3
v21.10.2
v21.10.1
v21.10
v21.08.6
v21.08.5
v21.08.4
v21.08.3
v21.08.2
v21.08.1
v21.08
v21.05.4
v21.05.3
v21.05.2
v21.05.1
v21.05
v21.04.6
v21.04.5
v21.04.4
v21.04.3
v21.04.2
v21.04.1
v21.04
v0.31.8
v0.31.7
v0.31.6
v0.31.5
v0.31.4
v0.31.3
v0.31.2
v0.31.1
v0.31.0
v0.30.7
v0.30.6
v0.30.5
v0.30.4
v0.30.3
v0.30.2
v0.30.1
v0.30.0
v0.29.3
v0.29.2
v0.29.1
v0.29.0
v0.28.3
v0.28.2
v0.28.1
v0.28.0
v0.27.5
v0.27.4
v0.27.3
v0.27.2
v0.27.1
v0.27
v0.26.4
v0.26.3
v0.26.2
v0.26.1
v0.26.0
v0.25.5
v0.25.4
v0.25.3
v0.25.2
v0.25.1
v0.25.0
v0.24.3
v0.24.2
v0.24.1
v0.24.0
v0.23.2
v0.23.1
v0.23.0
v0.22.0
v0.21.0
v0.20.3
v0.20.2
v0.20.1
v0.20.0
v0.19.0
v0.18.5
v0.18.4
v0.18.3
v0.18.2
v0.18.1
v0.18.0
v0.17.4
v0.17.3
v0.17.2
v0.17.1
v0.17.0
v0.16.3
v0.16.2
v0.16.1
v0.16.0
v0.15.3
v0.15.2
v0.15.1
v0.15.0
v0.14.3
v0.14.2
v0.14.1
v0.14.0
v0.13.1
v0.13.0
v0.12.2
v0.12.1
v0.12.0
v0.11.2
v0.11.1
v0.11.0
v0.10.0
v0.9.3
v0.9.2
v0.9.1
v0.9.0
v0.8.2
v0.8.1
v0.8.0
v0.7.6
v0.7.5
v0.7.4
v0.7.3
0.7.2
v.0.7.1
v0.7.0
v0.6.3
v0.6.2
v0.6.1
v0.6.0
v0.5.0
Labels
Clear labels
🎨 Design
📖 Docs Update
🐛 Bug
🐛 Bug
:cat2:🐈 Possible duplicate
💿 Database
☕ Open to discussion
💻 Front-End
🐕 Support
🚪 Authentication
🌍 Translations
🔌 API Task
🏭 Back-End
⛲ Upstream
🔨 Feature Request
🛠️ Enhancement
🛠️ Enhancement
🛠️ Enhancement
❤️ Happy feedback
🔒 Security
🔍 Pending Validation
💆 UX
📝 WYSIWYG Editor
🌔 Out of scope
🔩 API Request
:octocat: Admin/Meta
🖌️ View Customization
❓ Question
🚀 Priority
🛡️ Blocked
🚚 Export System
♿ A11y
🔧 Maintenance
> Markdown Editor
pull-request
Mirrored from GitHub Pull Request
No Label
🐕 Support
Milestone
No items
No Milestone
Projects
Clear projects
No project
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: starred/BookStack#2808
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking 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 @tdtmusic2 on GitHub (May 20, 2022).
Attempted Debugging
Searched GitHub Issues
Describe the Scenario
Hi everyone,
I have a fresh installation of Bookstack and I was trying to bind the AD to it, so users can login with their credentials. However, I can't seem to make it work, even after following everything I could find about this. My issue is exactly like the one here: https://github.com/BookStackApp/BookStack/issues/931
This is my .env ldap config:
When trying to login I get
ErrorException
ldap_bind(): Unable to bind to server: Invalid credentials
As a side note, how does the app handle OUs with spaces in their names? And also users with spaces in the name? When editing the .env file I noticed that after adding space the next word turns red, don't know if it's a problem or not.
Exact BookStack Version
22.04.2
Log Content
PHP Version
7.4.3
Hosting Environment
Ubuntu 20.04 virtual machine, installed via the official script.
@ssddanbrown commented on GitHub (May 21, 2022):
Hi @tdtmusic2,
Do you happen to have any special characters within your
LDAP_PASSvalue? Specifically a#?Spaces within
.envvalues should be fine as long as the whole value is wrapped in quotes.There should be no spaces between property names, the
=or the value though.@tdtmusic2 commented on GitHub (May 21, 2022):
Hi Dan. The first time I tried with a user that had : inside the password. After that, I tried with one that has $ at the beginning of the password. Could this be the issue? If so, I can set a password without special characters if needed.
@ssddanbrown commented on GitHub (May 21, 2022):
@tdtmusic2 I wouldn't have thought those would be an issue.
This is likely be an issue within one of the
LDAP_PASS,LDAP_DNorLDAP_SERVERoptions.Hard to know from my perspective, without full understanding of your LDAP environment.
You could test things using the ldapsearch command
, to assure you have correct and working server ,dn and pass options.
@tdtmusic2 commented on GitHub (May 22, 2022):
Ok, I reset the password for the Wiki user and this time used p@ssword1 and it seems that it worked. However, it said email confirmation is required but I didn't set up that, so I don't know if it's normal or not.
Anyway, there is clearly an issue with the password format, before this user I had another one with a password ending in # and it also did not work. OR it might be the fact that the OU for the previous user had space in its name (it's IT Support) and the Wiki user is in the IT OU, so no spaces.
About the environment, nothing special, just a Win Server 2016 DC and another one, identical, as secondary DC. But plenty of OUs, most of them with spaces in the name. And also all the users are required to have special characters in the password, so if this is the issue it will be a problem for them to login...
@ssddanbrown commented on GitHub (May 30, 2022):
This will be required if it's been enabled in the settings, or if the "Domain Restriction" registration setting is in use.
If this is instead referring to a box that requests the user to enter an email address, this can show if the system is not finding an email on the fetched LDAP user.
I have just re-tested things with an
LDAP_PASSvalue ofadmin#is@really£cool. This worked fine when properly quoted likeLDAP_PASS="admin#is@really£cool".Have not tested spaces in
LDAP_DNoption, since it would take a fair bit of extra time to test this on my setup, but have tested with spaces inLDAP_BASE_DNand that works fine, making me think spaces should not be a problem.Since you got things working I'll close this off but, if there's provable issues with specific mechanisms, they can be opened as new issues with specific reproduction steps.