I'm not picking up what you're putting down. Can you give me an example of the values in your LDAP repo and then the corresponding values that get created in Clearspace?
If I do an ldapsearch for my user, here is what I get back:
cn: Noah Campbell
Notice the two uid entries...
This is perfectly fine in OpenDirectory (and I'm guessing OpenLdap since that's what OpenDirectory essentially is). However, when I log into Clearspace, it consider noahc and noahcampbell as two different users, when they are in fact one.
Thanks Noah. I'll be honest: I don't have a ton of LDAP experience, but I've never seen that before. I'll have to float that around internally and see what people think about it.
Thanks for bringing this up. This is the first time I've seen that setup -- I wasn't aware any schema supported multiple uids if the DN was based on uid -- but apparently it is supported.
I'm glad to know authentication against multiple uids is working correctly in 1.x. It should continue to do so in 2.x (our new auth mechanisms are based on Acegi), and allow you to log in using either UID. I'll add a similar entry to our test LDAP server and see if I can reproduce the issue in both 2.x and 1.x as far as account creation is concerned. It should be just a matter of doing a search on uid, getting the DN, and creating a user based on the UID in the DN. Right now I believe the issue is that we have a 1:1 mapping between 'uid' in LDAP and Clearspace usernames.
Authentication works, but the UI breaks down. Note that I'm listed twice and permissions are tied to the id, not the dn. It's kinda annoying because I can't tell if I own the document or not.
clearcase ui.tiff 20.7 KB