Re: best practice for uid provisioning?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Scott Gilbert wrote:
I inherited an ldap with odd design. It has a custom
attribute as the rdn in the dn for all entries. The
rdn is not the uid. People entries are provisioned
automatically and users choose a uid after their entry
has been created for login purposes. The custom
attribute for the rdn serves as a unique identifier.
The uid is also unique.

I found that getting products to work with this ldap
is difficult because they expect the uid to be in the
dn.
Which products have problems?
Comments? Should I put the uid back in the dn?
Seems like it would make my life a lot simpler.
Sure.  A simple modrdn when the uid is assigned.
And what methods are best to create entries for users
without a uid? Maybe assign a temp and have them
change it? Or just assign them which is always the
easiest. Thanks.
Either way, but the former sounds like more work.
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
--
Fedora-directory-users mailing list
Fedora-directory-users@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-directory-users

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

--
Fedora-directory-users mailing list
Fedora-directory-users@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-directory-users

[Index of Archives]     [Fedora Directory Users]     [Fedora Directory Devel]     [Fedora Announce]     [Fedora Legacy Announce]     [Kernel]     [Fedora Legacy]     [Share Photos]     [Fedora Desktop]     [PAM]     [Red Hat Watch]     [Red Hat Development]     [Big List of Linux Books]     [Gimp]     [Yosemite News]

  Powered by Linux