test

Sun Java System Calendar Server 6.3 Administration Guide

15.3 Automatic Creation of Calendars

This section contains conceptual information and instructions for using the Calendar Server feature for automatically creating calendars upon a user's first login.

Automatic calendar creation is enabled by default. With it enabled, the system automatically creates calendars under two circumstances:

For the configuration information necessary to implement automatic creation of calendars in this circumstance, see To Configure Calendar Server for Groups.

This section covers the following topics:

15.3.1 Creating calids

Calendar Server creates the calendar ID (calid) for new default calendars from the user ID and the domain name.

For example, John Smith's user ID is jsmith, and his LDAP entry resides in the sesta.com domain. The first time he logs into Calendar Server, the system automatically creates a default calendar with jsmith@sesta.com as the calid. Each subsequent calendar John Smith creates has a calid with jsmith@sesta.com: prepended to the calendar name. For example, if John Smith later creates a new calendar named meetings, the calid for the new calendar is jsmith@sesta.com:meetings.

If a user, group, or resource without a default calendar is listed in the attendee list of an event, the system looks up the uid in LDAP in the event owner's domain as the event owner. If no domain is assigned to the owner, the default domain is assumed. The system constructs a calid by appending the domain to the uid.

If the system can't find the uid in the event owner's domain, it will search any other domains the event owner is allowed to search. For more information, see 11.2 Cross Domain Searching in Calendar Server 6.3 Systems.

ProcedureTo Enable Autoprovisioning of Calendars

The auto-creaton of calendars is enabled by default. However, if you need to turn it on again after disabling it, perform the steps that follow:

  1. Log in as an administrator with configuration privileges.

  2. Stop Calendar Server services by issuing the stop-cal command.

  3. Change to the /etc/opt/SUNWics5/cal/config directory.

  4. Save your old ics.conf file by copying and renaming it.

  5. Edit one or more of the following parameters in the Calendar Server configuration file, ics.conf, as shown in the following table:

    Parameters  

    Description and Default Value  

    local.autoprovision

    Set to “yes”, allows default calendar creation to occur automatically when the user logs in the first time. autoprovisioning is enabled by default. 

    To turn this feature off, set the value to “no”. 

  6. Verify that the user’s LDAP entry is enabled for calendar.

    The entry must contain the icsCalendarUser object class. Add the class to the user’s LDAP entry if it is not there.

  7. If your site is using multiple domains, the user’s domain must also be calendar enabled before autoprovisioning will work. The domain entry must contain the icsCalendarDomain object class.

  8. Save the file.

  9. Restart Calendar Server.

    cal-svr-base/SUNWics5/cal/sbin/start-cal

ProcedureTo Disable Autoprovisioning of Calendars

  1. Log in as an administrator with configuration privileges.

  2. Stop Calendar Server services by issuing the stop-cal command.

  3. Change to the /etc/opt/SUNWics5/cal/config directory.

  4. Save your old ics.conf file by copying and renaming it.

  5. Edit one or more of the following parameters in the Calendar Server configuration file, ics.conf, as shown in the following table:

    Parameters  

    Description and Default Value  

    local.autoprovision

    Setting the parameter to no disables autoprovisioning of user calendars.

  6. Save the file.

  7. Restart Calendar Server.

    cal-svr-base/SUNWics5/cal/sbin/start-cal

    Note –

    If autoprovisioning is disabled, calendars must be explicitly created for users before they can successfully log in.