Sun Java System Calendar Server 6.3 Administration Guide

1.5 End User Administration in Calendar Server Version 6.3

End users can connect to Calendar Server from client machines using a Web graphical user interface (GUI), Sun Java System Communications Express, or through the Connector for Microsoft Outlook, which allows end users to continue using Outlook on their desktop while still taking advantage of the Calendar Server back end. Users must have a unique entry in the LDAP directory. Each user can have one or more calendars and can belong to one or more groups.

Administrators, with the proper permissions, can add, delete or modify user LDAP entries, or resource LDAP entries, using the Delegated Administrator Utility (command-line) or Console (GUI).

For documentation on the Delegated Administrator Utility (commadmin), see Sun Java System Communications Services 6 2005Q4 Delegated Administrator Guide.

For documentation on the Delegated Administrator Console, see the Console's online help.

In addition, when necessary, you can use ldapmodify to modify LDAP entries directly. For information about ldapmodify, refer to the Sun ONE Directory Server Resource Kit 5.2 Tools Reference.

Caution – Caution –

Utility programs used in pre-Java Enterprise System deployments, such as csuser, are still bundled with Calendar Server. If you are using Access Manager in your deployment, do not use these utilities for managing or creating user, domain or resource LDAP entries. There are some exceptions. Where these apply, this guide will direct you to the proper utility.

This section describes the following aspects of user and user calendar administration:

1.5.1 Choosing the Proper User Management Tool for Calendar Server Version 6.3

Calendar users, groups, and resources can be administered using one of the following user management tools:

Note –

Delegated Administrator does not manage calendars. To create calendars for users, groups and resources, use the Calendar Server utilities cscal and csresource, or turn on autoprovisioning. With autoprovisioning turned on, the system creates a default calendar under two circumstances: if a user logs in without a default calendar, or a user, group or resource is issued an invitation before the default calendar exists.

1.5.2 Creating User LDAP Entries in Calendar Server Version 6.3

You can create users in LDAP using the following tools:

1.5.3 Authenticating Users in Calendar Server Version 6.3

Calendar Server requires a LDAP directory server such Sun Java System Directory Server to authenticate users (and to store user preferences).

1.5.4 Understanding User Preferences for Calendar Server Version 6.3

Calendar Server allows users to customize their views of calendar data by setting user preferences attributes, which are stored in the directory server. User preferences (as opposed to Calendar Server configuration parameters) refer to the user interface representation of calendar data and include items such as user name, email address, and preferred colors to use when rendering calendar views.

For a list of preferences, refer to the get_userprefs and set_userprefs WCAP commands in the Sun Java System Calendar Server 6.3 WCAP Developer’s Guide.

1.5.5 LDAP Groups Overview in Calendar Server Version 6.3

Groups are named collections of users. Each group has an LDAP entry, similar to a user or resource entry. You can use the same group entry for all services, such as calendar and messaging.

The following are a few facts about Calendar Server LDAP groups:

For more information about group calendars, see the following section: 1.5.7 Group Calendars Overview for Calendar Server Version 6.3.

1.5.6 Autoprovisioning: Automatic Creation of Calendars in Calendar Server Version 6.3

Calendar databases can be automatically populated by setting local.autoprovision="yes" in the ics.conf file. In addition, domains must be calendar enabled (have calendar service), meaning the domain LDAP entry must contain the icsCalendar object class.

There are two ways for default calendars to be created automatically:

For example, suppose tchang exists in the directory server but is not yet enabled for calendaring (that is, does not have a default calendar). With autoprovisioning turned on, and with the domain calendar enabled:

For more information about the configuration file parameters necessary for users, resources and groups, see 4.3 Configuring Calendar for LDAP Users, Groups and Resources.

1.5.7 Group Calendars Overview for Calendar Server Version 6.3

A group calendar can be created for any calendar-enabled LDAP group. This calendar can be scheduled much like an individual's calendar. Invitations sent to the group are scheduled to the group calendar and all individual member calendars. If a group calendar does not yet exist at the time it is invited to an event, and autoprovisioning is turned on, the system creates a calendar with a default set of properties and ACLs.

The following are some facts about group calendars:

For more information about Calendar Server users, see Chapter 14, Administering Users, Groups, and Resources.

1.5.8 Resources Overview for Calendar Server Version 6.3

A resource is anything that can be scheduled using a calendar, such as a conference room, or a projector. There is a separate resource LDAP entry for each such item. Create the LDAP entry and its associated calendar using the appropriate tools:

Note –

It is not necessary to explicitly create resource calendars. With autoprovisioning enabled, the first time a resource is invited, the system will automatically create a resource calendar for it. This is the same behavior as for users and groups.