Calendar Server users are created either manually or automatically:
Manually — If the Directory Server is configured for Schema 2, an administrator can add users to the directory server using Delegated Administrator and then create the users’ default calendars using the Calendar Server cscal utility.
If the Directory Server is configured for Schema 1, create both the user and the calendar at the same time using the Calendar Server csuser utility.
Automatically (autoprovisioning) — If autoprovisioning is configured and if the user already exists in the LDAP directory, then the first time that user logs in. Calendar Server automatically creates a default calendar.
In non-hosted domain mode, Calendar Server creates the calendar ID (calid) of the default calendar from the user ID. For example, if John Doe has a user ID of jdoe, his default calendar calid would be jdoe.
In hosted domain mode, the calid is a combination of the user ID and the user’s domain. For example, if John Doe is in domain example.com, and his user ID is jdoe, then his calid in a hosted domain environment is email@example.com.
For autoprovisioning to occur, the following criteria must be met:
The local.autoprovision parameter must be set to “yes” (which is the default) in the ics.conf file.
In hosted (virtual) domain mode, the domain must be calendar enabled. A domain is calendar enabled if its LDAP entry contains the icsCalendarDomain object class.
For example, suppose tchang exists in the directory server but is not yet enabled for calendaring (that is, does not have a default calendar). When tchang logs into Calendar Server for the first time, Calendar Server automatically enables tchang for calendaring and creates a default calendar with the calid tchang.