As a part of the migration from Exchange to JES we need to populate the attribute cn with a display name such as Donald C Shrum.  This will allow the Global Address List in Outlook clients connected to JES to show actual names as opposed to just an FSUID which is not always meaningful; Dave Borschel can provide more detail.

A note similar to the one below that describes the change and what needs to be done will be going out on Nolenet soon.  If you expect your changes to take more thnt a week to complete please email me and copy Dave Borschel with an estimate or best guess as to how much time you will need.

I encourage you to go ahead now and make the changes described below since uid is populated as described in production (in other words, it contains unique FSUIDs now).  This way you can make sure your systems/devices work OK before we actually start repopulating the cn attribute with the human-readable form of the person's name.

Donny
5-2236
--------
The Identity Management Team is changing the 'naming attribute' or 'relative distinguished name' (RDN) for all FSUIDs.  The naming attribute is the attribute used to uniquely identify each FSUID in our directory.

We will NOT be changing the naming attribute for the administrator or any proxy accounts.  For example, if you are using the proxy account "cn=ais-proxy,ou=proxy-users,dc=fsu,dc=edu" you do NOT need to change how you refer to this account in your code or LDAP configurations.

If you are reading any of our campus FSUID LDAP servers and searching by or for an FSUID you will need to use the attribute uid in place of cn.  For example, a pGina filter might read "(cn=%s)" and need to be changed to "(uid=%s)".  In short, references to cn should be replaced with uid.

If you write to any of our campus LDAP servers and you are dynamically pulling the RDN for each FSUID you modify you do not need to change anything. 

If you are explicitly constructing a RDN with code that might look as follows:

  $rdn = "cn=$fsuid,ou=people,dc=fsu,dc=edu"

you will need to modify your code to retrieve the RDN from our LDAP server and then make modifications based on the returned value. 

You can make the changes described above immediately.  The attribute uid is populated for all FSUIDs and dynamically retrieving the RDN for each modified entry will insure that when the naming attribute is changed your code will not be impacted.