Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
no, because that wouldn't be a legal x.500 format DN. You might wish to describe the actual scenarios and problems you're facing, rather than the way you think you want to fix the problem you have. a dn is NOT a username, it's just a unique obkect identifier within the LDAP database. You can use any attribute you wish as the username, e.g. email address, assuming that your front end supports it.
I am using a client that only binds to the LDAP server in the username@domainname format.
This format works fine with Active Directory, and is supposed to work with OpenLDAP too...
I have added the users with a simple username e.g. email@example.com, however the DN always ends up with the above mentioned format.
I see binding errors (in wireshark) when trying to login - error is "bad dn, invalid synthax)
It does work, again you need to define what attribute you are comparing the data against. You are very much wrong to think that AD is doing something different. an AD LDAP DN is exactly the same as an OpenLDAP DN. If it wasn't it wouldn't be legal LDAP.
You are seeing bind errors because, as I already said, that's not a valid DN, so will never be accepted as a DN by any LDAP service in the world. You need to look over your client, and see how it is configured to use which attributes of the object.
firstname.lastname@example.org is the same as testdomain.com\user1 for AD. So @ or \ are just separators. So it says that the user is user1 and the domain to log on is testdomain.com. Therefore the complete username is not email@example.com. The dn could look like something as cn=user1,...,dc=testdomain,dc=com, where the dots can be a number of organizational units.