Hi Quannah,
thanks for support. Now I understand little bit more ldif syntax/rules. Yes,
the source code is option as well, but I tried to avoid it :)
I know there is slapd.conf to cn=config converter, but unfortunately I was not
able to make it work (errors during conversion).
Thanks for he
Martin Stejskal wrote:
> I know there is slapd.conf to cn=config converter, but unfortunately I was not
> able to make it work (errors during conversion).
Could you please elaborate on that ideally with a slapd.conf for which the
conversion fails?
CIao, Michael.
smime.p7s
Description: S/MIME C
Ulrich,
You are correct, the development system is copied from the production
system. The process is to perform the same ldapsearch that is producing
a corrupted ldif from the development system against the production
system on my management system. I then scp the ldif file over to the
de
On Wed, 11 Jan 2017 at 3:15pm, Quanah Gibson-Mount wrote:
--On Wednesday, January 11, 2017 2:50 PM -0500 Frank Swasey
wrote:
My slapd.conf files are built using mustache templates with minimal
differences... Is there a specific config option I should be looking at
that could cause the op
Hello,
I have 2 LDAP servers:
-machine 1:" localserver.domain.com" : the DIT is
dn: dc=example
dc: bsr-ivv
objectClass: top
objectClass: dcObject
objectclass: organization
o: AAA
dn: ou=Users,dc=example
objectClass: top
objectClass: organizationalUnit
ou: Users
dn: ou=Groups,dc=example
objectClas
Hi Michael, Quannah and Howard,
thanks for great support.
I've some progress, but I did not solved/tested problem yet (working on it).
So I'll summarize my progress:
First of all, at Ubuntu 16 (and probably others as well) LDAP binary is
compiled without "meta" support -> that caused some
