October 2009 - calendarserver-dev - lists.macosforge.org

[CalendarServer] ApacheDirectoryService deleted
by CalendarServer 29 Oct '09

29 Oct '09

Deleted page "ApacheDirectoryService" by wsanchez(a)apple.com from 17.224.20.215* * The IP shown here might not mean anything if the user or the server is behind a proxy. -- CalendarServer </> HTTP/WebDAV/CalDAV Server This is an automated message. Someone at / added your email address to be notified of changes on ApacheDirectoryService. If it was not you, please report to .

1 0

[CalendarServer] WikiStart modified
by CalendarServer 29 Oct '09

29 Oct '09

Changed page "WikiStart" by wsanchez(a)apple.com from 17.224.20.215* Page URL: <http://trac.calendarserver.org/wiki/WikiStart> Diff URL: <http://trac.calendarserver.org/wiki/WikiStart?action=diff&version=41> Revision 41 -------8<------8<------8<------8<------8<------8<------8<------8<-------- Index: WikiStart ========================================================================= --- WikiStart (version: 40) +++ WikiStart (version: 41) @@ -7,8 +7,6 @@ = Documentation = * [wiki:docs-trunk CalendarServer-3.0 (in development)] - - * [wiki:DirectoryService Configuring directory services] * [wiki:CalDAVClientLibrary Client and Admin tool Library] -------8<------8<------8<------8<------8<------8<------8<------8<-------- * The IP shown here might not mean anything if the user or the server is behind a proxy. -- CalendarServer </> HTTP/WebDAV/CalDAV Server This is an automated message. Someone at / added your email address to be notified of changes on WikiStart. If it was not you, please report to .

1 0

[CalendarServer] docs-trunk modified
by CalendarServer 29 Oct '09

29 Oct '09

Changed page "docs-trunk" by wsanchez(a)apple.com from 17.224.20.215* Page URL: <http://trac.calendarserver.org/wiki/docs-trunk> Diff URL: <http://trac.calendarserver.org/wiki/docs-trunk?action=diff&version=11> Revision 11 -------8<------8<------8<------8<------8<------8<------8<------8<-------- Index: docs-trunk ========================================================================= --- docs-trunk (version: 10) +++ docs-trunk (version: 11) @@ -9,8 +9,8 @@ == Developers == - * [wiki:QuickStart Getting Started] - * [wiki:HACKING Developer's Guide to Hacking the Calendar Server] + * [wiki:QuickStart Getting started] + * [wiki:HACKING Developer's guide to hacking the Calendar Server] == Standards == -------8<------8<------8<------8<------8<------8<------8<------8<-------- * The IP shown here might not mean anything if the user or the server is behind a proxy. -- CalendarServer </> HTTP/WebDAV/CalDAV Server This is an automated message. Someone at / added your email address to be notified of changes on docs-trunk. If it was not you, please report to .

1 0

[CalendarServer] DirectoryService deleted
by CalendarServer 29 Oct '09

29 Oct '09

Deleted page "DirectoryService" by wsanchez(a)apple.com from 17.224.20.215* * The IP shown here might not mean anything if the user or the server is behind a proxy. -- CalendarServer </> HTTP/WebDAV/CalDAV Server This is an automated message. Someone at / added your email address to be notified of changes on DirectoryService. If it was not you, please report to .

1 0

[CalendarServer] DirectoryServices added
by CalendarServer 29 Oct '09

29 Oct '09

Added page "DirectoryServices" by wsanchez(a)apple.com from 17.224.20.215* Page URL: <http://trac.calendarserver.org/wiki/DirectoryServices> Content: -------8<------8<------8<------8<------8<------8<------8<------8<-------- [[Rst(/CalendarServer/trunk/doc/Admin/DirectoryServices.txt)]] -------8<------8<------8<------8<------8<------8<------8<------8<-------- * The IP shown here might not mean anything if the user or the server is behind a proxy. -- CalendarServer </> HTTP/WebDAV/CalDAV Server This is an automated message. Someone at / added your email address to be notified of changes on DirectoryServices. If it was not you, please report to .

1 0

[CalendarServer] docs-trunk modified
by CalendarServer 29 Oct '09

29 Oct '09

Changed page "docs-trunk" by wsanchez(a)apple.com from 17.224.20.215* Page URL: <http://trac.calendarserver.org/wiki/docs-trunk> Diff URL: <http://trac.calendarserver.org/wiki/docs-trunk?action=diff&version=10> Revision 10 -------8<------8<------8<------8<------8<------8<------8<------8<-------- Index: docs-trunk ========================================================================= --- docs-trunk (version: 9) +++ docs-trunk (version: 10) @@ -2,6 +2,9 @@ == Administration == + * [wiki:DirectoryServices Integrating with directory services] + * [wiki:XMLDirectoryService XML directory service] + * [wiki:OpenDirectoryService Open Directory directory service] * [wiki:ExtendedLogItems Extensions to the Apache access log file format] == Developers == -------8<------8<------8<------8<------8<------8<------8<------8<-------- * The IP shown here might not mean anything if the user or the server is behind a proxy. -- CalendarServer </> HTTP/WebDAV/CalDAV Server This is an automated message. Someone at / added your email address to be notified of changes on docs-trunk. If it was not you, please report to .

1 0

[CalendarServer] DirectoryService modified
by CalendarServer 29 Oct '09

29 Oct '09

Changed page "DirectoryService" by wsanchez(a)apple.com from 17.224.20.215* Page URL: <http://trac.calendarserver.org/wiki/DirectoryService> Diff URL: <http://trac.calendarserver.org/wiki/DirectoryService?action=diff&version=3> Revision 3 -------8<------8<------8<------8<------8<------8<------8<------8<-------- Index: DirectoryService ========================================================================= --- DirectoryService (version: 2) +++ DirectoryService (version: 3) @@ -1,47 +1,1 @@ -= Directory Services = - -The Calendar Server needs to be able to obtain information about the users, groups and resources ("principals") which access and/or have a presence on the server. - -== About principals == - -All principals have a "principal resource" on the server which represents the principal in the form of an HTTP resource. This is useful for obtaining information about a principal, such as the location of the principal's calendar home, the principal's members and/or memberships, and so on. This information is exposed via WebDAV properties on the principal resource. - -All principals can be used to configure access controls for resources on the server by granting or denying various privileges to the principal. - -Principals are also given a calendar home collection on the server, in which the principal may have one or more calendar collections, as well as special collections which allow the principals to schedule meetings with each other, etc. - -== The role of a directory service == - -A "directory service" is simply an entity which the server can ask for a list of principal types, a list of principals for a given type, and various information about an individual principal. Directory services are interchangeable, allowing the server to obtain this information from a variety of data store, such as configuration files or network directory systems such as LDAP. - -The directory service used by the server is configured in the `caldavd.plist` file by specifying the directory service implementation to use and it's options as a dictionary, provided as the value to the `DirectoryService` key: - -{{{ -<key>DirectoryService</key> -<dict> - <key>type</key> - <string>ExampleService</string> - - <key>params</key> - <dict> - <key>option</key> - <string>value</string> - </dict> -</dict> -}}} - -== Available implementations == - -The following directory service implementations are presently available: - - * [wiki:XMLDirectoryService XMLDirectoryService]: - this service is configurable via an XML file that contains principal information. - - * [wiki:OpenDirectoryService OpenDirectoryService]: - this service uses OpenDirectory (which in turn uses LDAP, Active Directory, etc.) - to obtain principal information. - - * [wiki:ApacheDirectoryService BasicDirectoryService and DigestDirectoryService]: - these services are configurable using configuration files in the same formats - as used by the Apache HTTP server, allowing you to use the same user/group setup - as a separately-running Apache server. +[[Rst(/CalendarServer/trunk/doc/Admin/DirectoryServices.txt)]] -------8<------8<------8<------8<------8<------8<------8<------8<-------- * The IP shown here might not mean anything if the user or the server is behind a proxy. -- CalendarServer </> HTTP/WebDAV/CalDAV Server This is an automated message. Someone at / added your email address to be notified of changes on DirectoryService. If it was not you, please report to .

1 0

[CalendarServer] OpenDirectoryService modified
by CalendarServer 29 Oct '09

29 Oct '09

Changed page "OpenDirectoryService" by wsanchez(a)apple.com from 17.224.20.215* Page URL: <http://trac.calendarserver.org/wiki/OpenDirectoryService> Diff URL: <http://trac.calendarserver.org/wiki/OpenDirectoryService?action=diff&versio…> Revision 5 -------8<------8<------8<------8<------8<------8<------8<------8<-------- Index: OpenDirectoryService ========================================================================= --- OpenDirectoryService (version: 4) +++ OpenDirectoryService (version: 5) @@ -1,36 +1,1 @@ -= !OpenDirectoryService = - -This [wiki:DirectoryService directory service] uses [http://www.apple.com/server/macosx/features/opendirectory.html OpenDirectory] (which in turn uses LDAP, Active Directory, etc.) to obtain principal information. - -For more information about configuring OpenDirectory services, see Apple's [http://images.apple.com/server/pdfs/Open_Directory_v10.4.pdf Open Directory Administration] document. - -== Configuring the Calendar Server == - -The full name of the implementation class is `twistedcaldav.directory.appleopendirectory.OpenDirectoryService` and the service takes a `node` parameter which contains the name of the directory node to bind to. - -For example: - -{{{ - -<key>DirectoryService</key> -<dict> - <key>type</key> - <string>twistedcaldav.directory.appleopendirectory.OpenDirectoryService</string> - - <key>params</key> - <dict> - <key>node</key> - <string>/Search</string> - </dict> -</dict> -}}} - -The special OpenDirectory node `/Search` causes the server to bind to the default directory search path that the host the server is running on is configured to use. To bind to a specific LDAP service, a node of the form `/LDAPv3/ldapserver.example.com` would be appropriate. - -== OpenDirectory/LDAP Schema Requirements == - -browser:CalendarServer/trunk/doc/ical-schema.txt - -== Binding the host to Open Directory == - -TBD. +[[Rst(/CalendarServer/trunk/doc/Admin/DirectoryService-OpenDirectory.txt)]] -------8<------8<------8<------8<------8<------8<------8<------8<-------- * The IP shown here might not mean anything if the user or the server is behind a proxy. -- CalendarServer </> HTTP/WebDAV/CalDAV Server This is an automated message. Someone at / added your email address to be notified of changes on OpenDirectoryService. If it was not you, please report to .

1 0

[CalendarServer] XMLDirectoryService modified
by CalendarServer 29 Oct '09

29 Oct '09

Changed page "XMLDirectoryService" by wsanchez(a)apple.com from 17.224.20.215* Page URL: <http://trac.calendarserver.org/wiki/XMLDirectoryService> Diff URL: <http://trac.calendarserver.org/wiki/XMLDirectoryService?action=diff&version…> Revision 7 -------8<------8<------8<------8<------8<------8<------8<------8<-------- Index: XMLDirectoryService ========================================================================= --- XMLDirectoryService (version: 6) +++ XMLDirectoryService (version: 7) @@ -1,85 +1,1 @@ -= XMLDirectoryService = - -This [wiki:DirectoryService directory service] is configurable via an XML file that contains principal information. - -== Configuring the Calendar Server == - -The full name of the implementation class is `twistedcaldav.directory.xmlfile.XMLDirectoryService` and the service takes an `xmlFile` parameter which contains the name of the XML file to read principal information from. - -For example: - -{{{ - -<key>DirectoryService</key> -<dict> - <key>type</key> - <string>twistedcaldav.directory.xmlfile.XMLDirectoryService</string> - - <key>params</key> - <dict> - <key>xmlFile</key> - <string>/etc/caldavd/accounts.xml</string> - </dict> -</dict> -}}} - -The service re-reads the XML file if it's timestamp changes, so edits to the XML file should not require a server restart. - -== Configuring principals == - -A "principal" is WebDAV terminology for an "identifier" that can be used for authentication and access control purposes. Typically it is used to represent the users of the system, as well as other types of items needing some "presence" on the system. - -The principals supported by the XMLDirectoryService are: - - * `users`: individual (typically human) users of the system - * `groups`: a group of other principals (can be a mixture of any of the principal types) - * `locations`: rooms or locations where meetings can be held - * `resources`: inanimate objects that also need to be part of a meeting (e.g., a projector) - -Principals are expressed in an XML document. The root element `accounts` has an attribute `realm` which describes the authentication realm. It contains principal elements which, in turn contain elements describing the principal. The element itself (`user`, `group`, `location`, `resource`) denotes the "type" of the principal. - - * `uid`: the login identifier for the principal. - * `guid`: the unique identifier for the principal - must be unique on this server at least. - * `password`: the principal's password in plain text. - * `name`: the principal's full name (or description). - * `members`: contains a list of `uid`s for the principals which are members of the principal being defined. A principal that has members is termed a "group principal". Only principals of type "group" should be configured to have members. The `members` element has `member` sub-elements used to specify each member. The `member` element has a `type` attribute that defines the principal type of the member (one of `users`, `groups`, `locations` and `resources`), and the text value inside the `member` element is the corresponding `uid` of the principal being referenced. Any type of principal may be a member of a group, including other groups. You should avoid creating "loops" by having two groups reference each other. - * `cuaddr`: a calendar user address for the principal. Calendar user addresses must be URIs and must be unique to the principal (ie. the same calendar user address may not be used to identify multiple principals). Note that the server will add it's own calendar user address to principals (eg. the principal's URI on the server is always a valid calendar user address). Multiple `cuaddr` elements may be provided for a principal. The calendar user address is the identifier used for sending inviting principals to meetings. - * `disable-calendar`: when present, this element indicates that the specified principal is able to login to the calendar server, but is not setup with a calendar and cannot do scheduling. This type of principal is typically used to allow access to a shared group calendar without having to setup a "personal" calendar account for the user. This element can only be specified on `user` and `group` principal types. - * `auto-schedule`: when present, this element indicates that the server will automatically process scheduling messages for the corresponding principal. i.e. when a scheduling message arrives, if it does not conflict with an existing meeting it will be automatically accepted and "booked" into the principal's main calendar, or if it does conflict it will be automatically declined. This element can only be defined on `location` and `resource` principal types. - * `proxies`: this element contains a list of `member` elements that define which other principals have read-write proxy/delegate access to the corresponding principal's calendar data. - -For example: - -{{{ -<?xml version="1.0" encoding="utf-8"?> -<accounts realm="Test Realm"> - <user> - <uid>admin</uid> - <password>admin</password> - <name>Super User</name> - </user> - <user> - <uid>test</uid> - <password>test</password> - <name>Test User</name> - <cuaddr>mailto:testuser@example.com</cuaddr> - </user> - <group> - <uid>users</uid> - <password>users</password> - <name>Users Group</name> - <members> - <member type="users">test</member> - </members> - </group> - <location> - <uid>mercury</uid> - <password>mercury</password> - <name>Mecury Conference Room, Building 1, 2nd Floor</name> - <auto-schedule/> - <proxies> - <member type="users">test</member> - </proxies> - </location> -</accounts> -}}} +[[Rst(/CalendarServer/trunk/doc/Admin/DirectoryService-XML.txt)]] -------8<------8<------8<------8<------8<------8<------8<------8<-------- * The IP shown here might not mean anything if the user or the server is behind a proxy. -- CalendarServer </> HTTP/WebDAV/CalDAV Server This is an automated message. Someone at / added your email address to be notified of changes on XMLDirectoryService. If it was not you, please report to .

1 0

[CalendarServer] #352: Missing kerberos module
by CalendarServer 29 Oct '09

29 Oct '09

#352: Missing kerberos module -----------------------------+---------------------------------------------- Reporter: cweger@… | Owner: wsanchez@… Type: Defect | Status: new Priority: 5: Not set | Milestone: Component: Calendar Server | Severity: Crash/data loss Keywords: kerberos | -----------------------------+---------------------------------------------- Following the build instructions on the wiki page, I successfully built the GUI app. Launching this app results in an immediate error dialog: ImportError: No module named kerberos I'm not a python person, so it's possible I've done something stupid to cause this error. -- Ticket URL: <http://trac.calendarserver.org/ticket/352> CalendarServer </> HTTP/WebDAV/CalDAV Server

1 2