Multiple Domains Active Directory LDAP Authentication #459

Open
opened 2026-02-04 20:11:38 +03:00 by OVERLORD · 16 comments
Owner

Originally created by @777string on GitHub (Oct 4, 2017).

Desired Feature:
Multiple Domains Active Directory LDAP Authentication

Originally created by @777string on GitHub (Oct 4, 2017). Desired Feature: Multiple Domains Active Directory LDAP Authentication
OVERLORD added the 🔨 Feature Request🚪 Authentication labels 2026-02-04 20:11:38 +03:00
Author
Owner

@genxlee commented on GitHub (Oct 4, 2017):

Would be nice

@genxlee commented on GitHub (Oct 4, 2017): Would be nice
Author
Owner

@doc-jay commented on GitHub (May 8, 2018):

I'm currently needing this functionality, came here to look for it. Any plans on implementing it?

Thank you for all of your hard work on bookstack!

@doc-jay commented on GitHub (May 8, 2018): I'm currently needing this functionality, came here to look for it. Any plans on implementing it? Thank you for all of your hard work on bookstack!
Author
Owner

@cb3inco commented on GitHub (Mar 29, 2019):

@ssddanbrown does Bookstack support this?

@cb3inco commented on GitHub (Mar 29, 2019): @ssddanbrown does Bookstack support this?
Author
Owner

@Cidwill commented on GitHub (Jan 28, 2022):

Being able to configure additional LDAP addresses would be great for resilience as we operate multiple DCs for logon handling whereas Bookstack relies on just one of them being up and running.

Assuming it's not possible to configure currently I'd love for this to be implemented in the future.

@Cidwill commented on GitHub (Jan 28, 2022): Being able to configure additional LDAP addresses would be great for resilience as we operate multiple DCs for logon handling whereas Bookstack relies on just one of them being up and running. Assuming it's not possible to configure currently I'd love for this to be implemented in the future.
Author
Owner

@samip5 commented on GitHub (Mar 2, 2022):

Current state with multiple servers defined in .env:

Screenshot 2022-03-02 at 13 04 19

@samip5 commented on GitHub (Mar 2, 2022): Current state with multiple servers defined in .env: <details> ![Screenshot 2022-03-02 at 13 04 19](https://user-images.githubusercontent.com/1703002/156349997-0cd17151-d954-445e-ac37-992e79074b25.png) </details>
Author
Owner

@joaomezzari commented on GitHub (Mar 22, 2023):

+1 for this one

@joaomezzari commented on GitHub (Mar 22, 2023): +1 for this one
Author
Owner

@luizstange1 commented on GitHub (Mar 22, 2023):

+1 for this one

@luizstange1 commented on GitHub (Mar 22, 2023): +1 for this one
Author
Owner

@almirhoepers commented on GitHub (Mar 22, 2023):

+1 for this one

@almirhoepers commented on GitHub (Mar 22, 2023): +1 for this one
Author
Owner

@ArthurBVB commented on GitHub (Mar 22, 2023):

+1 for this one

@ArthurBVB commented on GitHub (Mar 22, 2023): +1 for this one
Author
Owner

@ssddanbrown commented on GitHub (Mar 22, 2023):

@joaomezzari @luizstange1 @almirhoepers @ArthurBVB Please just use the 👍 reaction on the initial post, instead of adding such comments which will notify all those watching this thread, and please don't group-spam a thread like that.

@ssddanbrown commented on GitHub (Mar 22, 2023): @joaomezzari @luizstange1 @almirhoepers @ArthurBVB Please just use the :+1: reaction on the initial post, instead of adding such comments which will notify all those watching this thread, and please don't group-spam a thread like that.
Author
Owner

@KNMK79 commented on GitHub (Mar 30, 2023):

Maybe this will work for you too, try and define only the domain in the LDAP_SERVER setting. On most systems it is accepted that DNS then chooses one of multiple domain controllers... works for us.

@KNMK79 commented on GitHub (Mar 30, 2023): Maybe this will work for you too, try and define only the domain in the LDAP_SERVER setting. On most systems it is accepted that DNS then chooses one of multiple domain controllers... works for us.
Author
Owner

@PeteDiCo commented on GitHub (Jul 25, 2023):

Question: Does anyone know if it supports all domain in a forest / subdomains in LDAP/AD?
I can authenticate when my base dn is LDAP_BASE_DN="dc=domain,dc=local", but it doesn't seem so read into "dc="sub",dc=domain,dc=local"

@PeteDiCo commented on GitHub (Jul 25, 2023): Question: Does anyone know if it supports all domain in a forest / subdomains in LDAP/AD? I can authenticate when my base dn is LDAP_BASE_DN="dc=domain,dc=local", but it doesn't seem so read into "dc="sub",dc=domain,dc=local"
Author
Owner

@Gameink commented on GitHub (Aug 1, 2023):

Is there any Roadmap on when this feature will be added? Or is it possible to realize this setup now? :)

@Gameink commented on GitHub (Aug 1, 2023): Is there any Roadmap on when this feature will be added? Or is it possible to realize this setup now? :)
Author
Owner

@jefry7 commented on GitHub (Aug 31, 2023):

This function is also very interesting. How to add?

@jefry7 commented on GitHub (Aug 31, 2023): This function is also very interesting. How to add?
Author
Owner

@otherjoel commented on GitHub (Sep 1, 2023):

This is the kind of enterprise feature that businesses should have to pay for IMO.

@otherjoel commented on GitHub (Sep 1, 2023): This is the kind of enterprise feature that businesses should have to pay for IMO.
Author
Owner

@jefry7 commented on GitHub (Mar 12, 2025):

This is the kind of enterprise feature that businesses should have to pay for IMO.

Who can I talk to about this topic?

@jefry7 commented on GitHub (Mar 12, 2025): > This is the kind of enterprise feature that businesses should have to pay for IMO. Who can I talk to about this topic?
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/BookStack#459