well, there's really no standard rule on what cn should contain..
It's used in many instances as the full name of the person, but in other
instances it's used as a unique id at that level of the tree..
Unfortunately the ldap backend is hardcoded to use that attribute for
full_name, so there's
hi,
i dont know the answer to your question... but wouldnt it be correct if your ldap server was made up like this:
cn=givenname surname etc
sn=surname
gn=givenname
uid=I0112233
and the dn:
uid=I0112233,dc=example,dc=org
cn is supposed to be the name of the entity, so i think evolution is
Hi,
I've got Evolution doing proper LDAP looks against our LDAP server
except for one problem. Our LDAP system uses a USER ID as the cn, i.e.
cn=I0112233. So browsing the LDAP contacts under Other Contacts or
trying to send an email to someone looked up via LDAP results in the
name being
