September 2008 - calendarserver-dev

Hoping for a sanity check
by Mark Cockfield 29 Oct '08

29 Oct '08

Greetings, I am developing an RIA in Flex which needs to be built upon a calendaring foundation. After discovering that the CalendarServer is the Holy Grail I have not only found my foundation, but a good part of my infrastructure as well. Really nice work! Now imagine my disappointment upon realizing that Actionscript has been apparently locked down to only allow GET and POST http methods. After considerable thrashing about I seem to be faced with the following two options: 1. Code my own HTTP client in Actionscript at the socket level. 2. Use PyAMF and the Twisted Gateway to hook a Remote Messaging interface into the Calendar Service. As I don't really relish the thought of #1, and though I'm still fairly early in the Python/Twisted/PyAMF/CalendarServer learning curve, I think #2 might have some merit. The current line of reasoning is that in cluster.py where the memccahed and notification processes are being added to monitor a twisted gateway process could be added as well. Then in tap.py, after site = Site(realRoot), "site" could be added to the gateway as the remote object to call...? The idea being that you would simply send HTTP requsts in an array through the AMF channel to the appropriate method on the server. So what I'm hoping for is that someone might be able to tell me I am either out of my mind, or better yet, on the right track. Any thoughts would be greatly appreciated. Mark

6 15

[CalendarServer] #300: Add support for ifb (VFREEBUSY) files via GET
by CalendarServer 28 Oct '08

28 Oct '08

#300: Add support for ifb (VFREEBUSY) files via GET -------------------------------+-------------------------------------------- Reporter: helge(a)zideone.com | Owner: wsanchez(a)apple.com Type: Enhancement | Status: new Priority: 5: Not set | Milestone: Component: Calendar Server | Version: Severity: Other | Keywords: -------------------------------+-------------------------------------------- CalendarServer currently does not support retrieving regular VFREEBUSY (.vfb, .ifb) resources via a regular HTTP GET. Support for GETable freebusy files would be very helpful since almost any calendar client (including Outlook) already supports that. My suggestion is to add a virtual 'freebusy.ifb' resource below each calendar _and_ one below each principal. Example: {{{ /users/user01/calendar/freebusy.ifb /principals/__uids__/user01/freebusy.ifb }}} Another option would be {{{ /users/user01/calendar.ifb }}} It would be very good for caching if the resources would have an etag. Eg in the case of calendar collection freebusy resources that could be derived from the collections ctag. -- Ticket URL: <https://trac.calendarserver.org/ticket/300> CalendarServer </> HTTP/WebDAV/CalDAV Server

1 5

[ANNOUNCE] PyKerberos 1.1
by Guido Günther 19 Sep '08

19 Sep '08

Hello everybody, I've tagged version 1.1 of PyKerberos in Subversion. It can be downloaded via: svn co http://svn.calendarserver.org/repository/calendarserver/PyKerberos/tags/rel… PyKerberos is a high-level Python wrapper for Kerberos/GSSAPI operations. Instead of wrapping the entire Kerberos/GSSAPI framework, PyKerberos instead offers a limited set of functions that do what is needed for client/server Kerberos authentication based on <http://www.ietf.org/rfc/rfc4559.txt>. The API provided can be found at: http://svn.calendarserver.org/repository/calendarserver/PyKerberos/tags/rel… Besides the usual bunch of bug fixes the most visible changes in this release are: * gsswrap/unwrap support (Guido Günther, Jelmer Vernooij) * ftp-gss client example application (Jelmer Vernooij) * password changing support (Guido Günther) * portability improvements (Wilfredo Sánchez Vega) * testsuite cleanups (Cyrus Daboo) Cheers, -- Guido P.S.: for those prefering a tarball: http://honk.sigxcpu.org/projects/pykerberos/PyKerberos-1.1.tar.gz (md5sum 26d2d5cbb300ff147614be521feb059f)

1 0

Welcome Guido Günther
by Wilfredo Sánchez Vega 18 Sep '08

18 Sep '08

Guido Günther is the first external developer to get commit access to the Calendar Server project. It probably took us longer to get around to making this happen than it should have, but I hope it's the beginning of a long-term trend towards an increasingly open development community. Welcome aboard, Guido. -wsv

3 4

[CalendarServer] #288: Missed keytab entry cleanup.
by CalendarServer 17 Sep '08

17 Sep '08

#288: Missed keytab entry cleanup. ------------------------------+--------------------------------------------- Reporter: bland(a)bbnest.net | Owner: wsanchez(a)apple.com Type: Defect | Status: new Priority: 2: Expected | Milestone: Component: PyKerberos | Version: Severity: Other | Keywords: ------------------------------+--------------------------------------------- There is a missed keytab entry celanup here: http://trac.calendarserver.org/browser/PyKerberos/trunk/src/kerberosgss.c#L… Expected krb5_free_keytab_entry_contents(kcontext, &entry); bellow this line. -- Ticket URL: <http://trac.calendarserver.org/ticket/288> CalendarServer </> HTTP/WebDAV/CalDAV Server

1 4

[CalendarServer] #281: all invocations of PyCObject_Check(pystate) should return a meaningful exception
by CalendarServer 17 Sep '08

17 Sep '08

#281: all invocations of PyCObject_Check(pystate) should return a meaningful exception -----------------------------+---------------------------------------------- Reporter: agx(a)sigxcpu.org | Owner: wsanchez(a)apple.com Type: Defect | Status: new Priority: 5: Not set | Milestone: Component: PyKerberos | Version: Severity: Other | Keywords: -----------------------------+---------------------------------------------- without this we see: SystemError: error return without exception set which is not very helpful -- Ticket URL: <https://trac.calendarserver.org/ticket/281> CalendarServer </> HTTP/WebDAV/CalDAV Server

1 2

[CalendarServer] ProxyCleanup modified
by CalendarServer 16 Sep '08

16 Sep '08

Changed page "ProxyCleanup" by cdaboo(a)apple.com from 17.101.32.44* Page URL: <http://trac.calendarserver.org/wiki/ProxyCleanup> Diff URL: <http://trac.calendarserver.org/wiki/ProxyCleanup?action=diff&version=3> Revision 3 -------8<------8<------8<------8<------8<------8<------8<------8<-------- Index: ProxyCleanup ========================================================================= --- ProxyCleanup (version: 2) +++ ProxyCleanup (version: 3) @@ -1,8 +1,8 @@ -== Problem: == +== Problem: Server logs show lots of: "Unable to find any record with GUID XXX" errors after deleting users from the directory. == The problem here is that the deleted users were referenced as proxy for some other users and the proxy database is not part of the directory but separately maintained by the calendar server (since that behavior is specific to the server). Since proxies are managed via access control on the calendar server, often when someone makes a request of the server, the access control list has to be evaluated and the list of users in the proxy list expanded. That is when the missing GUIDs show up. You can run a special "proxy cleanup" tool to remove the deleted GUIDs from the proxy db and stop these errors from occurring. -== How to run a tool to clean-out missing GUIDs from the proxy database == +=== How to run a tool to clean-out missing GUIDs from the proxy database === Here is a python script that can be run to clean-up the proxy DB: -------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 ProxyCleanup. If it was not you, please report to .

1 0

[CalendarServer] FAQ modified
by CalendarServer 16 Sep '08

16 Sep '08

Changed page "FAQ" by cdaboo(a)apple.com from 17.101.32.44* Page URL: <http://trac.calendarserver.org/wiki/FAQ> Diff URL: <http://trac.calendarserver.org/wiki/FAQ?action=diff&version=4> Revision 4 -------8<------8<------8<------8<------8<------8<------8<------8<-------- Index: FAQ ========================================================================= --- FAQ (version: 3) +++ FAQ (version: 4) @@ -16,7 +16,5 @@ Most Python modules are written in Python, and therefore platform-independant, but the Calendar Server uses several C extension modules. Make sure that your Python and all C extension modules are built for the same architecture. -Server logs show lots of: "Unable to find any record with GUID XXX" errors after deleting users from the directory. What's up? +[wiki:ProxyCleanup Server logs show lots of: "Unable to find any record with GUID XXX" errors after deleting users from the directory. What's up?] - The problem here is that the deleted users were referenced as proxy for some other users and the proxy database is not part of the directory but separately maintained by the calendar server (since that behavior is specific to the server). Since proxies are managed via access control on the calendar server, often when someone makes a request of the server, the access control list has to be evaluated and the list of users in the proxy list expanded. That is when the missing GUIDs show up. You can run a special "[wiki:ProxyCleanup proxy cleanup]" tool to remove the deleted GUIDs from the proxy db and stop these errors from occurring. - -------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 FAQ. If it was not you, please report to .

1 0

[CalendarServer] ProxyCleanup modified
by CalendarServer 16 Sep '08

16 Sep '08

Changed page "ProxyCleanup" by cdaboo(a)apple.com from 17.101.32.44* Page URL: <http://trac.calendarserver.org/wiki/ProxyCleanup> Diff URL: <http://trac.calendarserver.org/wiki/ProxyCleanup?action=diff&version=2> Revision 2 -------8<------8<------8<------8<------8<------8<------8<------8<-------- Index: ProxyCleanup ========================================================================= --- ProxyCleanup (version: 1) +++ ProxyCleanup (version: 2) @@ -1,5 +1,8 @@ -== Describes how to run a tool to clean-out missing GUIDs from the proxy database == +== Problem: == +The problem here is that the deleted users were referenced as proxy for some other users and the proxy database is not part of the directory but separately maintained by the calendar server (since that behavior is specific to the server). Since proxies are managed via access control on the calendar server, often when someone makes a request of the server, the access control list has to be evaluated and the list of users in the proxy list expanded. That is when the missing GUIDs show up. You can run a special "proxy cleanup" tool to remove the deleted GUIDs from the proxy db and stop these errors from occurring. + +== How to run a tool to clean-out missing GUIDs from the proxy database == Here is a python script that can be run to clean-up the proxy DB: -------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 ProxyCleanup. If it was not you, please report to .

1 0

[CalendarServer] ProxyCleanup added
by CalendarServer 16 Sep '08

16 Sep '08

Added page "ProxyCleanup" by cdaboo(a)apple.com from 17.101.32.44* Page URL: <http://trac.calendarserver.org/wiki/ProxyCleanup> Content: -------8<------8<------8<------8<------8<------8<------8<------8<-------- == Describes how to run a tool to clean-out missing GUIDs from the proxy database == Here is a python script that can be run to clean-up the proxy DB: [https://trac.calendarserver.org/browser/CalendarServer/trunk/bin/proxyclean… proxyclean] To use this do the following: 1. Download the script to the calendar server machine 1. Stop the calendar server 1. Backup the /Library/CalendarServer/Documents/principals/.db.calendaruserproxy file (will need to sudo to see that) 1. Run: {{{sudo python proxyclean}}} 5. Examine the records that it reports. Check that the GUIDs returned correspond to some of those reported in the server log. 5. If everything looks OK at this point, re-run the tool with the -c option to actually fix the db: {{{sudo python proxyclean -c}}} 7. Run one more time without -c to verify that fixed it. 7. Restart the calendar server. 7. Verify that the missing principals errors are gone. If users report that proxies are all missing after running this tool, then shut down the calendar server and restore the backed-up .db.calendaruserproxy file. -------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 ProxyCleanup. If it was not you, please report to .

1 0