[Date Prev][Date Next]
str2entry: invalid value for attributeType userCertificate #0 (syntax 18.104.22.168.4.1.1422.214.171.124.8) ???
- To: <email@example.com>
- Subject: str2entry: invalid value for attributeType userCertificate #0 (syntax 126.96.36.199.4.1.14188.8.131.52.8) ???
- From: "Marcum, Bob" <Bob.Marcum@telecheck.com>
- Date: Wed, 11 Jul 2007 15:38:38 -0600
- Content-class: urn:content-classes:message
- In-reply-to: <46952C09.firstname.lastname@example.org>
- Thread-index: AcfD8I4b0bjzzXaiQfuhs0wBoaoU8AAEYPjA
- Thread-topic: str2entry: invalid value for attributeType userCertificate #0 (syntax 184.108.40.206.4.1.14220.127.116.11.8) ???
I am attempting to add some records to an ldap using slapadd and an ldif
Here is the ldif entry:
userCertificate: -----BEGIN PUBLIC KEY-----
-----END PUBLIC KEY-----
displayName: " "
businessCategory: " "
description: " "
When I execute slapadd I get the error message shown above in the
subject line and the report that "slapadd: could not parse entry
(line=59)", which is the line after the compete entry, that is, after
'description: "" '.
I do not understand what is going on. I have done this before
successfully many times with the very same ldif file (I am sure!) What
I have tried several formats for the userCertificate value: 1) using
Unicode representatons of the newlines (that is the one that has worked
in the past) 2) using ascii \n representations of the newlines.
None of these approaches now seem to work. Please help. Thanks!!
The information in this message may be proprietary and/or
confidential, and protected from disclosure. If the reader of this
message is not the intended recipient, or an employee or agent
responsible for delivering this message to the intended recipient,
you are hereby notified that any dissemination, distribution or
copying of this communication is strictly prohibited. If you have
received this communication in error, please notify First Data
immediately by replying to this message and deleting it from your