Frank Offermanns wrote:
> This all looks correct. You simply have to correctly parse the LDIF output.
>
> See RFC 2849 for the details. And use a decent LDIF parser for your favourite
> scripting language and not some home-grown bash/sed/awk/whatever
> scripts which
> fail for such a simple
Frank Offermanns wrote:
>
> > I hope this makes things clearer.
> > Tell me if I should make an ITS.
>
> That's called "Base64 encoding". Go decode your encoded value, I think
> you'll be happy.
>
The current ldif exports are not encoded, so what should I decode?
The old was, as it shoul
> This all looks correct. You simply have to correctly parse the LDIF
output.
>
> See RFC 2849 for the details. And use a decent LDIF parser for your
favourite
> scripting language and not some home-grown bash/sed/awk/whatever
> scripts which
> fail for such a simple thing.
>
I am not quit
Frank Offermanns wrote:
I am sorry that I confused you.
I hope this samples make thinks clear:
New Ldif Content:
"dn: cn=hghg,cn=InitialUser,ou=Users,o=caesar
cn: hghg
FileContent:
This is the content of my file. As you can see it is not encoded. Therefor
I can not be imported since ; : blanks,
>
> > I hope this makes things clearer.
> > Tell me if I should make an ITS.
>
> That's called "Base64 encoding". Go decode your encoded value, I think
> you'll be happy.
>
The current ldif exports are not encoded, so what should I decode?
The old was, as it should be.
To be more clear:
Wi
--On Tuesday, May 05, 2015 9:39 AM +0200 Frank Offermanns
wrote:
I hope this makes things clearer.
Tell me if I should make an ITS.
That's called "Base64 encoding". Go decode your encoded value, I think
you'll be happy.
--Quanah
--
Quanah Gibson-Mount
Platform Architect
Zimbra, Inc.
-
I am sorry that I confused you.
I hope this samples make thinks clear:
New Ldif Content:
"dn: cn=hghg,cn=InitialUser,ou=Users,o=caesar
cn: hghg
FileContent:
This is the content of my file. As you can see it is not encoded. Therefor
I can not be imported since ; : blanks,
carriage return etc ar
Frank Offermanns wrote:
Hello,
in our custom schema we have used several attributes with the syntax:
1.3.6.1.4.1.1466.115.121.1.5
attributetype ( myAttributeType:106 NAME ( 'casFileContent' )
DESC 'Contains the file'
SYNTAX 1.3.6.1.4.1.1466.115.121.1.5
SINGLE-VALUE )
p.org
Datum: 04.05.2015 20:04
Betreff: Re: Need migrationhelp for 1.3.6.1.4.1.1466.115.121.1.5
because of bug in slapcat
Gesendet von: "openldap-technical"
--On Monday, May 04, 2015 3:08 PM +0200 Frank Offermanns
wrote:
> Hello,
>
> in our custom schema we have used
--On Monday, May 04, 2015 3:08 PM +0200 Frank Offermanns
wrote:
Hello,
in our custom schema we have used several attributes with the syntax:
1.3.6.1.4.1.1466.115.121.1.5
attributetype ( myAttributeType:106 NAME ( 'casFileContent' )
DESC 'Contains the file'
SYNTAX 1.3.6.1.4.1.1
10 matches
Mail list logo
