Can anyone shed any light on :
slapadd: could not parse entry (line=234) str2entry: attributeType userCertificate #0: needs ';binary' transfer as per syntax 184.108.40.206.4.1.14220.127.116.11.8
This is ocurring when running 2.4.x slapadd on a certificate containing a binary attribute, which was a slapcat from a 2.3.X openldap server.
The attribute in question is already a binary attribute, there is a double colon after the certificate name, so i gather it just wants userCertificate;binary:: as the attribute name in the LDIF dump when loading ? Cant simply search and replace, because that will increase the line length, which will stop it from parsing.
Alternatively, anybody know of any tool which can re-justify line lengths in an ldif, if i search and replace the attribute name ?
It might be nice to have some sort of non-default legacy flag, for loading a previous release's ldif (or at least be more forgiving than the present parser)