[Date Prev][Date Next]
(ITS#8166) translucent overlay - compatibility with other overlays that need write access
- To: openldap-its@OpenLDAP.org
- Subject: (ITS#8166) translucent overlay - compatibility with other overlays that need write access
- From: firstname.lastname@example.org
- Date: Mon, 08 Jun 2015 08:07:22 +0000
- Auto-submitted: auto-generated (OpenLDAP-ITS)
Full_Name: Thomas Keil
OS: Debian 8.0 Jessie
Submission from: (NULL) (22.214.171.124)
This is a software enhancement request.
I have the following use case at hand:
My university provides a central LDAP directory which authenticates users but
does not contain group information. For my institute we want to set up our own
OpenLDAP server which relays the user authentication to the central directory
(via back_ldap) but additionally provides group information. This should be used
by a network of linux machines for user authentication, group management and
login filtering. For reasons of high availability we want to replicate our local
LDAP server using the builtin replication mechanism of OpenLDAP.
This seems to be a nice example for the use of the translucent backend.
Nevertheless group membership (for login filtering) can only be provided using
the memberof overlay which (so it seems) is not compatible with the translucent
Furthermore the syncprov overlay needs to access the lastmod attribute which is
disabled for databases using the translucent overlay. Thus a local database
combined with the translucent overlay cannot be replicated at all.
To me it seems that these problems can be solved by allowing write access to the
local database for other overlays when used in combination with the translucent
overlay. It would make this overlay much more useful than it is right now since
it would allow to use this in large scale deployments as well (where replication
is essential). This is valid especially for cases where the local administration
has no write access to the central directory.