[Date Prev][Date Next] [Chronological] [Thread] [Top]

RE : RE : RE : Non ASCII char in dn?

Can you paste the line where is says invalid syntax? I just encoded the
file UTF-8 using notepad and it put some weird char at the beginning of
the file so when I tryed to import it I got that invalid syntax error so
I edited the file with pico and there was 2-3 char in the beginning of
the file I deleted and it worked afterwards

I'm using OpenLDAP 2.0.15 with the schemas that came with it.

I'm using Outlook XP and when you search the entries with it they show
up fine.

Hope this helps

Jean-Rene Cormier

-----Message d'origine-----
De : Sylvain Amrani [mailto:NO_SPAM@samrani.com] 
Envoyé : 13 avril, 2002 08:59
À : Jean-Rene Cormier
Cc : 'Pierangelo Masarati'; 'OpenLDAP List'
Objet : Re: RE : RE : Non ASCII char in dn?

"Jean-Rene Cormier" <jrclist@cipanb.ca> writes:

> Well finally got it to work. :) It was because when I encoded it UTF-8
> it put some weird chars at the beginning of the file I just deleted
> and it worked.
> I don't mind having the dn base64 encoded since I'm using LDAP
> Administrator and it decodes them for me ;)
> Jean-Rene Cormier

Still doesn't work for me... I tried to create a new person entry with
some UTF-8 chars in the CN attribute, but the server responds «invalid
syntax». I use the 2.0.14 and 2.0.23 releases.

What is your openldap release ?
What file with weird chars are your talking about ? An ldif one ?

Which are the schemas and attributes used ?

Sorry for all this questions, but I've got an other silly one :

If your put some non-ascii chars in the DN, and CN and SN attributes,
what happens when your search these entries with common tools such as
OutLook, Netscape and so on ?

I don't really understand the schema files syntax. There's no SYNTAX
rule in the CN attribute in core.schema. So can it really accept UTF-8
chars ?

Thanks for your answers

Sylvain Amrani
sam at samrani dot com