Repository navigation
Replies: 8 comments 20 replies
|
Hi, is this planned for any next release? |
|
Hi @vharseko, that's awesome !!! I've compiled the source with PR #1292 and have a question: What if you want to have base dn of If it's meant to have many proxy backends (one for each sub base DN) then how do you combine all of them under the parent umbrella of Thanks |
|
@vharseko, attribute-mapping is also very helpful and very needed, but it looses the original attribute. For instance Also virtual attributes like this would be helpful in the future: |
|
Hi @bilias, The OUD identity choices you described are now available in PR #1292, in commit 848238df74. The new
Microsoft AD DS does not implement Proxied Authorization V2, so an AD route must use The local userRoot or LDIF backend solution you found is appropriate for publishing the parent entry such as Certificate validation is currently lazy: creating the discovery mechanism does not contact remote servers, so a missing or untrusted certificate is reported when the proxy first opens a remote connection or performs an The administration guide now documents all four modes, their setup requirements, risks, and the AD limitation. Testing the OpenLDAP, 389 DS, and AD parts of your topology would be valuable, especially both allowed and denied operations for |
|
@vharseko nice ! some notes:
And one issue. When all LDAP servers are down for a backend (for example sub2) (but other backends work ok) then all queries return this: The error 91 is not good for some applications. I've seen this with OUD as well and the way I solved this was to create an LDIF backend that apart from the base Some questions:
|
|
New feature request: Example from OUD: |
Uh oh!
There was an error while loading. Please reload this page.
LDAP Proxy Backend
Overview
An LDAP Proxy Backend is a specialized intermediary service that acts as a gateway between LDAP clients (users, applications, devices) and one or more backend LDAP directory servers (e.g., Microsoft Active Directory, OpenLDAP, FreeIPA). It processes, filters, and routes LDAP requests without being the authoritative source of the directory data itself, enhancing security, performance, and manageability.
Key Features & Functions
1. Request Routing & Load Balancing
2. Security & Access Control
3. Protocol Translation & Normalization
4. Caching
5. Abstraction & Federation (Virtual Directory)
6. Centralized Logging & Auditing
Common Use Cases
Technical Summary
In architectural terms, the LDAP Proxy Backend functions as a facade. It implements the LDAP protocol to appear as a standard server to clients, while its core logic involves processing requests (
bind,search,compare) and intelligently communicating with the authoritative directories behind it.Vote to raise the priority 🖐️
All reactions