By Joesciallo-Oracle on Apr 13, 2007
When it comes to renaming UIDs of Communications Suite users--a common request--the old adage, "Don't Try This at Home," or even, "Don't Try This at All," surely applies.
You all know the story: one of your existing users has had a name change (whether by marriage, divorce, divine intervention, or some other reason), and now you need to rename the user. The quick and dirty advice is to not even considering renaming the UID, but instead, to rename other aspects of the user's entry, such as cn, mail attribute, and other 'visible handles' to the mailbox, calendar, and address book. You can configure Comms servers to enable users to authenticate using email address or any other per-user attributes instead of the default UID. But leave that UID alone, unless you want to get snake-bit.
There's lots of history on this topic and lots of folks much-well versed in it than I am. This is definitely a topic upon which we could--and should--create a definitive white paper. However, be that as it may, we're stuck with this situation. And lest you think this is just Sun as usual, it turns out we're not the only company suffering from it. According to our experts, some others include Ipswitch IMail, Lotus Domino, Novell Netware, qmail, and SAS LDAP. This is an industry-wide problem.
The bottom line is that we do recognize this is a huge issue (there are RFEs filed), lots of products face this issue, and you can't use or depend upon UID as a unique identifier. Given time, I'd like to see what I could do to document this labyrinth for our customers. No promises exactly, but this strikes me as a topic that would serve everyone well and prevent some headaches if we took some time to capture it once and for all.