The scheme I've found most useful is to assign a unique identifier to each user. Something completely meaningless, like a lowercase letter followed by a bunch of digits (that pattern will work as an ID in most NOS or non directory systems like AD, NDS, Unix, NT SAM, etc). Just increment the numeric suffix as you assign each new ID. Using e-mail like aliases is generally a pain because it requires you to change the ID every time you have a name change. Same is true for IDs that are tied to a user's role (like using different letter prefixes for employees and temps). It's usually pretty easy to build a routine into your user provisioning software that will increment the ID value automatically. Any provisioning software that won't let you do this should get rejected out of hand (with a pointed memo to the vendor giving the reason for the rejection). Getting any enterprise, especially one where system administration is decentralized, to adopt a common ID scheme is almost always difficult and usually requires considerable effort on the 8th layer of the OSI model -- Politics.
Phil Lembo
-- Fedora-directory-users mailing list Fedora-directory-users@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-directory-users
