Hi, I'm trying to insert userCertificate values containing
x500UniqueIdentifiers. When the value appears at the SubjectNames, it
inserts correctly.
By this I assume there is a validation for the field formatting.
When I have a x500UniqueIdentifier at the IssuerNames it fails to
insert.
Hey,
I recently started to get used to Red Hat Enterprise 6 with openldap 2.4
and the main migration point is the 'new' config style.
I removed my test-database (I have a ldif-backup) files and the default
config from my testsystem.
I followed the RH guide [1], but now get an error with my
--On Wednesday, December 08, 2010 6:36 PM +0100 Marc Patermann
hans.mo...@ofd-z.niedersachsen.de wrote:
Hi,
Marc Patermann schrieb am 06.12.2010 16:40 Uhr:
what could the following possibly be?
When I do a
# slapadd -q -v -c -l dump.ldif
to a SLES 11 SP1 (openldap 2.3.20)
I get this after
Marc Patermann wrote:
Hi,
Marc Patermann schrieb am 06.12.2010 16:40 Uhr:
what could the following possibly be?
This looks like something valgrind ought to be able to diagnose.
When I do a
# slapadd -q -v -c -l dump.ldif
to a SLES 11 SP1 (openldap 2.3.20)
I get this after a few 1000
Juan Gonzalez wrote:
Hi, I’m trying to insert userCertificate values containing
x500UniqueIdentifiers. When the value appears at the SubjectNames, it inserts
correctly.
By this I assume there is a validation for the field formatting.
When I have a x500UniqueIdentifier at the IssuerNames it
Howard Chu wrote:
Juan Gonzalez wrote:
Hi, I’m trying to insert userCertificate values containing
x500UniqueIdentifiers. When the value appears at the SubjectNames, it inserts
correctly.
By this I assume there is a validation for the field formatting.
When I have a x500UniqueIdentifier at the
