Calendar Server 6.3 - Change the CN: Attribute of a Resource Calendar Created by csresource (Doc ID 1348174.1)

Last updated on MAY 31, 2022

Applies to:

Goal

• Provide basic description of RDN
• Provide basic description of possible Directory Server configuration requirements
• Provide example session of changing calendar resource's cn: attribute

Use case

The usage of calendar resources has evolved since the initial release of Calendar Server 6.3.  In some situations, an administrator may need to change the common name (cn) of a resource calendar so that Convergence users can find it when searching ("Subscribe" and "Reservations" features).

(See Also: Convergence 2 + Calendar Server 6.3: Common Issues with Resource Calendars [ID 1339483.1])

Problem

When csresource creates the LDAP entry for the resource, it uses "cn" in the RDN.  (The RDN is the left-most named pair in a dn:).

By convention, most of the entries created in the Communications Suite org tree use "uid=".

The RDN cannot be changed with the normal ldapmodify commands.  "modrdn" must be used instead of "modify".

The Communication Suite products do not support changing the uid, so "fixing" the dn by using uid in the RDN of entries complements the behavior of the suite.

Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.