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

[CalendarServer] #331: groups disabled for calendaring... why ?
by CalendarServer 29 Apr '09

29 Apr '09

#331: groups disabled for calendaring... why ? ------------------------------+--------------------------------------------- Reporter: jduffas1@… | Owner: wsanchez@… Type: Feature | Status: new Priority: 5: Not set | Milestone: Component: Calendar Server | Severity: Other Keywords: | ------------------------------+--------------------------------------------- In the latest code, groups have been explicitly disabled for calendaring, I don't think it's a good idea, unless there is a good reason like a security reason. I (and perhaps other peoples) would apreciate if it could be back. jean -- Ticket URL: <http://trac.calendarserver.org/ticket/331> CalendarServer </> HTTP/WebDAV/CalDAV Server

1 1

[CalendarServer] #323: cat command on a directory returns HTML page
by CalendarServer 29 Apr '09

29 Apr '09

#323: cat command on a directory returns HTML page -------------------------------------+-------------------------------------- Reporter: mail@… | Owner: cdaboo@… Type: Defect | Status: new Priority: 5: Not set | Milestone: Component: CalDAV Client | Severity: Other Keywords: | -------------------------------------+-------------------------------------- Since Linux upgrade to Lenny, the command 'cat' of 'CalDAVClientLibrary/runshell.py' returns HTML instead of an ics text if the argument is a directory. E.g. calling 'cat calendars/users/me/calendar/f0e947e9.ics' works fine, but 'cat calendars/users/me/calendar' returns the same HTML page, as if you use a web browser (<html><head><title>Collection listing for /calendars/users...). -- Ticket URL: <http://trac.calendarserver.org/ticket/323> CalendarServer </> HTTP/WebDAV/CalDAV Server

1 1

Re: [CalendarServer-dev] [CalendarServer] #272: Fix epydoc/pydoctor build
by CalendarServer 29 Apr '09

29 Apr '09

#272: Fix epydoc/pydoctor build ------------------------------------+--------------------------------------- Reporter: agx@… | Owner: wsanchez@… Type: Defect | Status: closed Priority: 5: Not set | Milestone: Component: Calendar Server | Severity: Other Resolution: Documentation changed | Keywords: ------------------------------------+--------------------------------------- Changes (by wsanchez@…): * status: new => closed * resolution: => Documentation changed Comment: Fixed in r4112 Guido, feel free to just commit this sort of thing if you like. -- Ticket URL: <http://trac.calendarserver.org/ticket/272#comment:1> CalendarServer </> HTTP/WebDAV/CalDAV Server

1 0

Re: [CalendarServer-dev] [CalendarServer] #268: Proxy list not updating when read/write proxy added
by CalendarServer 29 Apr '09

29 Apr '09

#268: Proxy list not updating when read/write proxy added ---------------------------------+------------------------------------------ Reporter: mail@… | Owner: cdaboo@… Type: Defect | Status: new Priority: 5: Not set | Milestone: Component: CalDAV Client | Severity: Other Keywords: | ---------------------------------+------------------------------------------ Description changed by wsanchez@…: Old description: > When using the command line shell to add a read/write proxy the list of > proxies isn't updated correctly. Reproduce as follows... > > (assuming logged in) > proxies -i > list > add -w > <add a proxy> > list > [ proxy will not be shown in list] > add -w > [ proxy will now be shown ] > q <don't add a proxy, just quit> > list > [ proxy will now be shown in list ] > > This works OK when adding a read-only proxy. New description: When using the command line shell to add a read/write proxy the list of proxies isn't updated correctly. Reproduce as follows... {{{ (assuming logged in) proxies -i list add -w <add a proxy> list [ proxy will not be shown in list] add -w [ proxy will now be shown ] q <don't add a proxy, just quit> list [ proxy will now be shown in list ] }}} This works OK when adding a read-only proxy. -- -- Ticket URL: <http://trac.calendarserver.org/ticket/268#comment:1> CalendarServer </> HTTP/WebDAV/CalDAV Server

1 0

[CalendarServer] #334: CalDAVClientLibrary Kerberos authentication
by CalendarServer 29 Apr '09

29 Apr '09

#334: CalDAVClientLibrary Kerberos authentication ----------------------------------------+----------------------------------- Reporter: rziai@… | Owner: cdaboo@… Type: Defect | Status: new Priority: 3: Important | Milestone: Component: CalDAV Client | Severity: Other Keywords: | ----------------------------------------+----------------------------------- CalDAVClientLibrary is the way to go for setting ACLs and various other things but it does not support Kerberos authentication. On the other hand, using Kerberos is the recommended authentication method of CalendarServer. The attached patch adds Kerberos support to the library, using the PyKerberos binding. -- Ticket URL: <http://trac.calendarserver.org/ticket/334> CalendarServer </> HTTP/WebDAV/CalDAV Server

1 4

Re: [CalendarServer-dev] [CalendarServer] #269: Need an abstraction layer for accessing calendar data.
by CalendarServer 29 Apr '09

29 Apr '09

#269: Need an abstraction layer for accessing calendar data. -----------------------------+---------------------------------------------- Reporter: dreid@… | Owner: wsanchez@… Type: Defect | Status: new Priority: 2: Expected | Milestone: CalendarServer-2.x Component: Calendar Server | Severity: Other Keywords: | -----------------------------+---------------------------------------------- Changes (by wsanchez@…): * milestone: CalendarServer-2.2 => CalendarServer-2.x -- Ticket URL: <http://trac.calendarserver.org/ticket/269#comment:2> CalendarServer </> HTTP/WebDAV/CalDAV Server

1 0

Re: [CalendarServer-dev] [CalendarServer] #269: Need an abstraction layer for accessing calendar data.
by CalendarServer 29 Apr '09

29 Apr '09

#269: Need an abstraction layer for accessing calendar data. -----------------------------+---------------------------------------------- Reporter: dreid@… | Owner: wsanchez@… Type: Defect | Status: new Priority: 2: Expected | Milestone: CalendarServer-2.2 Component: Calendar Server | Severity: Other Keywords: | -----------------------------+---------------------------------------------- Changes (by wsanchez@…): * milestone: => CalendarServer-2.2 -- Ticket URL: <http://trac.calendarserver.org/ticket/269#comment:1> CalendarServer </> HTTP/WebDAV/CalDAV Server

1 0

How to 'enable' locations and resources for OD configuration
by Eli Bach 29 Apr '09

29 Apr '09

From reading cachingappleopendirectory.py (and looking through the debug log), if the resource/location isn't already in the memcache, it queries DirectoryServices for the matching recordname (which it finds), but then it appears to check if the resource/location is part of the restrictedgroup (which I have configured). Since resource/location have no group attribute, this always fails. Or am I misunderstanding how this works? Eli

2 1

[CalendarServer] #335: Search via email address in cachingappleopendirectory fails
by CalendarServer 29 Apr '09

29 Apr '09

#335: Search via email address in cachingappleopendirectory fails ------------------------------+--------------------------------------------- Reporter: ebach2@… | Owner: wsanchez@… Type: Defect | Status: new Priority: 1: Blocker | Milestone: Component: Calendar Server | Severity: Serious Keywords: | ------------------------------+--------------------------------------------- Using trunk/head, with users in opendirectory, ldap set to /127.0.0.1 instead of /Search, with iCal from 10.5.6, if I connect as user 'dave', and create an event inviting user 'sarah(a)test.com', iCal will auto- complete the name fine and pass the email address to DCS. However, in the case where the cache misses (user sarah hasn't connected since the server was last started), it does an OD search for sarah(a)test.com, which fails to find the user (there is a user with that address in emailaddress, verified both with a DS dumping tool I wrote and in Directory.app). However, if I first make sure that user sarah has connected, then her info gets loaded into the cache, and she is properly invited to the event. -- Ticket URL: <http://trac.calendarserver.org/ticket/335> CalendarServer </> HTTP/WebDAV/CalDAV Server

1 7

[CalendarServer] #333: LDAP Schema
by CalendarServer 29 Apr '09

29 Apr '09

#333: LDAP Schema -------------------------------------+-------------------------------------- Reporter: alex@… | Owner: wsanchez@… Type: Defect | Status: new Priority: 5: Not set | Milestone: Component: Calendar Server | Severity: Other Keywords: | -------------------------------------+-------------------------------------- The schema file is missing from the repository. -- Ticket URL: <http://trac.calendarserver.org/ticket/333> CalendarServer </> HTTP/WebDAV/CalDAV Server

1 1