Please note that the final change; updating the value in the attribute cn will occur this Sunday.  The original announcement follows:

The attribute cn needs to be populated with a human readable name such as “Shrum, Donald C”  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.  Additionally, this will make the naming attribute the default attribute for iPlanet (uid) as opposed to the default as it was when FSUIDs were housed in Novell’s eDirectory (cn.)

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.  This change will take place on June 1, 2008.

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.

The Identity Management Team will change the value in the attribute cn from an individual’s FSUID to a full name such as “Shrum, Donald C”  This change will take place on June 15, 2008.

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 find some example code here:  http://fsuid.fsu.edu/admin/project-history/05-21-2008.html

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.

If you have questions you can feel free to contact me at 5-2236

Donny Shrum