mirror of
https://github.com/BookStackApp/BookStack.git
synced 2026-07-16 05:33:49 +03:00
LDAP stoppped working (Active Directory) #5413
Closed
opened 2026-02-05 10:02:54 +03:00 by OVERLORD
·
14 comments
No Branch/Tag Specified
development
l10n_development
release
snyk-action
ci_and_static
mfa_key
phpstan_june26
MilnerMart/development
GamerClassN7/impersonations-for-admin
Zhey-on/feature/csp-image-css-controls-6033
tortillas5/development
llm_only
vectors
McTom234/oidc-key-algorithms
captcha_example
v26.05.2
v26.05.1
v26.05
v26.03.5
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
🐛 Bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: starred/BookStack#5413
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 @Utility9298 on GitHub (Aug 28, 2025).
Describe the Bug
Hi everyone,
my LDAP setup does not seem to work anymore. No minor changes were made on the LDAP server (active directory) or bookstack, except default system updates.
My .env does look like this:
Steps to Reproduce
Expected Behaviour
Login does work
Screenshots or Additional Context
No response
Browser Details
No response
Exact BookStack Version
V25.07
@ssddanbrown commented on GitHub (Aug 28, 2025):
Hi @Utility9298,
Can you share the log line just before the content you shared? The most important line should be about one line above what's provided, and will typically start with the log date/time.
Also, please confirm your exact host operating system, and its exact version.
@Utility9298 commented on GitHub (Aug 28, 2025):
I did some more testing:
I can succesfully run ldapsearch as user www-data with my given configuration.
This let's me think it is likely a bookstack issue.
@Utility9298 commented on GitHub (Aug 28, 2025):
Hi @ssddanbrown
here is the beginning of the log file:
I am runnning ubuntu 24.04.3 with bookstack v25.07
As mentioned above, I can sucessfully run ldapsearch from command line directly...
@ssddanbrown commented on GitHub (Aug 28, 2025):
Looking at your config, I see
LDAP_SERVER=ldaps://domain.name:636.ldapsearchtests use specifically also useldaps(not LDAP over STARTTLS) with the exact same port and host as configured in BookStack?@Utility9298 commented on GitHub (Aug 28, 2025):
Hi @ssddanbrown,
yes LDAPS is working on 636:
I never was able to get it running with LDAP over STARTTLS, that's why I am using LDAPS.
When I change my .env to:
I do receive following error in
storage/logs/laravel.log:Where can I find the application log according to the error message? Was not able to find it in the documentation...
@bpelaia commented on GitHub (Aug 28, 2025):
Hi Utility9298,
in env you have set:
in log it reports:
Please try setting LDAP_START_TLS to false.
Best regards,
B.
@ssddanbrown commented on GitHub (Aug 28, 2025):
It's that log, with the referenced message being the line above that message in the log.
That text is primarily for display in the UI.
The original error shared represents a more fundamental connection error.
Are you actually using a
.localaddress, or was that just for the example? Just considering since.localcould throw some extra considerations into the mix (eg. reliance on mdns or.locallocal DNS handling).As an extra test, you could try running something like this (changing the host name) from the BookStack host system to check if a more basic tcp connection can be made via the LDAPS port to that host:
@Utility9298 commented on GitHub (Aug 29, 2025):
@bpelaia setting LDAP_START_TLS to false does work. I can login via LDAP...
@ssddanbrown sadly the domain name really ends on .local ... I know this is not recommended, it's an older environment and it already was like this when I started working here.
I will talk to my boss, we will most likely change domain name soon...
I wil do some further testing, if I find something interesting I will tell you!
@Utility9298 commented on GitHub (Aug 29, 2025):
When I run
openssl s_client -debug -connect company.local:389 -starttls ldap -showcertseverything seems fine. The connection seems trusted on the bookstack server, so it should even work withLDAP_START_TLS=true@ssddanbrown commented on GitHub (Aug 29, 2025):
@Utility9298 What about the php command in my last message?
Often requests via PHP may not use system-level configuration (like certs, proxy env options, etc...) like command line tooling, so I'm interested to see if there's a difference in that respect here.
Also, just to help understand the environment, I'm assuming you're using a custom cert?
Is there a custom CA cert in use added to the BookStack host machine for that then?
@Utility9298 commented on GitHub (Sep 1, 2025):
@ssddanbrown
I see, when i run
php -r "echo (fsockopen('domain.local', 636, \$a, \$b, 3) ? 'Connected' : 'Failed');"the command line changes to
Connecteduser@bookstackv1:/var/www/bookstack$...Is this behaviour expected? I do not receive any error messages
I am using a custom cert yes, the certificate authority is installed as trusted CA on the ubuntu host.
@ssddanbrown commented on GitHub (Sep 1, 2025):
@Utility9298 Okay, so that indicates a working route to port 636 of your LDAP domain.
For LDAP, PHP uses openldap configuration.
I would have thought that the ldapsearch cli uses the same config and libraries, but maybe that's an incorrect assumption.
On the system, you should find a
/etc/ldap/ldap.conffile.Edit that. By default I think you'd see a
TLS_CACERT /etc/ssl/certs/ca-certificates.crtline.Try specifically updating that line to be your custom CA cert.
Restart any running php services afterwards to ensure changes may be picked up:
For reference, documentation for the
ldap.conffile can be seen here:https://www.openldap.org/software//man.cgi?query=ldap.conf&sektion=5&apropos=0&manpath=OpenLDAP+2.4-Release
@Utility9298 commented on GitHub (Sep 1, 2025):
@ssddanbrown
I did change
/etc/ldap/ldap.conf/to my custom ca cert.LDAPS does not work as before.
But LDAP with StartTLS does work now :)
So i guess I will stay with LDAP with StartTLS now. Thank you very much for your help!
@ssddanbrown commented on GitHub (Sep 2, 2025):
Awesome, glad to hear that things are now working!