Hmm, thats strange, but with GQ-1.0b1 I'm getting the same results
- can change anything in the contacts except CN - will produce the same
error like Evo.
Looks to me like there is problem in Openldap or Evo and GQ share the
same bug. Is someone else running Openldap 2.1.22 experiencing this
behavior?
David
On Sat, 24. 04. 2004 v 00:26, Tony Earnshaw:
> fre, 23.04.2004 kl. 11.43 skrev Adam Tauno Williams:
>
> > > searching through history of this list I've found mail from Tony
> > > Earnshaw giving some example on subject. Looking at snippet bellow
> > > I just wonder if it's legal to have different 'cn' value in
> > > distinguishedName and in 'cn' entity?
> >
> > No, it is not legal. The RDN(s) must exist in object itself.
>
> CN is multivalued (Openldap 2.2.10, GQ 1.0.b1). You can give it as many
> different values as you wish, and each may be different from the rDN.
>
> *shrug*
>
> --Tonni
--
David Kmoch
Technical University of Liberec
Department of Applied Informatics
Halkova 6, 461 17 Liberec
tel: +420 485 353 633
fax: +420 485 353 112
_______________________________________________
evolution maillist - [EMAIL PROTECTED]
http://lists.ximian.com/mailman/listinfo/evolution
