back-ldap redirect RootDSE? RWM re-encode attributes?

To: openldap-technical@openldap.org

Subject: back-ldap redirect RootDSE? RWM re-encode attributes?

From: B Galliart <bgallia@gmail.com>

Date: Fri, 20 Jul 2018 19:51:14 -0500

Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=m5gr9e8Yy4+fJOQI7PXRw76V6QD+fNJ3EWr09LNxTa8=; b=txiLyhTFm5Jp6YXjkbSqNcKg3FzBn5AUeKFwpF2VMePDesQSBalGzruJLfGp/xPqrC +rU2S19zugqEAegnNS3v6rKjixikuHoNt+IvVtm9hZDjk2jQvH41D1v6fR6hpRqppn5b odyqr7IiYPkWzBx3VkhExbLaKumRS+bb9kMsrLKVA9k+jXXxczbv5tl1NS5GSKrjfjnC ylj4C8MbaC5TZmZO2q2vzA7rwBBVHthp7kpwRwhWpaC30wFlx2b3Y6rHFHtvq1yQM5jB 2cZfcDRmU2wb574ThIEf9J6L8T10m4XdBpYnvnag/83FmWTMY761i48ZMgyQhs721gWs RAyw==

I am trying to use OpenLDAP slapd to proxy to multiple LDAP servers but run into some issues with how the LDAP client application is written. I wondered if anyone has any suggestions for doing either of the following with slapd:

(1) Can the back-ldap suffix override the RootDSE of the OpenLDAP server so that all RootDSE requests get proxied?

(2) Is there a way with the RWM or a different overlay to convert specific attributes to hex or MIME before passing it back to the LDAP client? For example, if an attribute is given to back-ldap as a BLOB, can it convert the BLOB to hex before passing it along?

It would be nice to have the option to do both of the above but for my current situation being able to do just one or the other would work.

Thanks