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

[CalendarServer] #277: Set process name
by CalendarServer 26 Oct '09

26 Oct '09

#277: Set process name --------------------------------+------------------------------------------- Reporter: wsanchez(a)apple.com | Owner: wsanchez(a)apple.com Type: Defect | Status: new Priority: 3: Important | Milestone: 2.x Component: Calendar Server | Version: Severity: Other | Keywords: --------------------------------+------------------------------------------- Server should do `setproctitle` or whatever to set the process name so that it isn't `python`, which makes it harder to distinguish from other python programs. I think this would require a C extension, since Python doesn't provide API for it. -- Ticket URL: <https://trac.calendarserver.org/ticket/277> CalendarServer </> HTTP/WebDAV/CalDAV Server

1 2

[CalendarServer] #274: caldavd does not properly quote parameters
by CalendarServer 26 Oct '09

26 Oct '09

#274: caldavd does not properly quote parameters ---------------------------------+------------------------------------------ Reporter: kmdurbrow(a)gmail.com | Owner: wsanchez(a)apple.com Type: Defect | Status: new Priority: 5: Not set | Milestone: Component: Calendar Server | Version: Severity: Other | Keywords: ---------------------------------+------------------------------------------ Last line of caldavd {{{ ${configfile} }}} should be quoted -- Ticket URL: <https://trac.calendarserver.org/ticket/274> CalendarServer </> HTTP/WebDAV/CalDAV Server

1 2

[CalendarServer] #319: A solution is needed when max_allowed_instances is exceeded.
by CalendarServer 26 Oct '09

26 Oct '09

#319: A solution is needed when max_allowed_instances is exceeded. -----------------------------+---------------------------------------------- Reporter: apm@… | Owner: wsanchez@… Type: Defect | Status: new Priority: 5: Not set | Milestone: Component: Calendar Server | Severity: Serious Keywords: | -----------------------------+---------------------------------------------- With the ability to create events longer into the future the possibility that a user will create an event with more than "max_allowed_instances" (currently 1000) increases. From instance.py: # The maximum number of instances we will ezpand out to. # Raise a TooManyInstancesError exception if we exceed this. max_allowed_instances = 1000 ... which will make events disappear from instance 1000 or not get created at all if you place the mother event sufficiently far back in the past. If - say - your default_future_expansion_duration is 2 years, you currently cannot create a daily recurring event with a motherevent before ~ april 2008. Or if you create a daily recurring event today, it will no longer work after 1000 days. I see no good solution to this without some mechanism for the user to clean up old calendars, so the don't unnecessarily contain - say - 5 year old daily events. -- Ticket URL: <http://trac.calendarserver.org/ticket/319> CalendarServer </> HTTP/WebDAV/CalDAV Server

1 2

[CalendarServer] #286: ./run script have Perl run-time dependency.
by CalendarServer 13 Sep '09

13 Sep '09

#286: ./run script have Perl run-time dependency. ------------------------------+--------------------------------------------- Reporter: bland(a)bbnest.net | Owner: wsanchez(a)apple.com Type: Enhancement | Status: new Priority: 4: Nice to have | Milestone: Component: Calendar Server | Version: trunk Severity: Other | Keywords: ------------------------------+--------------------------------------------- ./run script uses xpath utility to fetch values out of caldavd.plist. This utility is Perl based and adds excessive dependency to CalendarServer bundle. It will be nice to switchover to PyXML inline code instead. -- Ticket URL: <https://trac.calendarserver.org/ticket/286> CalendarServer </> HTTP/WebDAV/CalDAV Server

1 2

UID/GUID/Shortname chaos?
by Peter Mogensen 28 Aug '09

28 Aug '09

Looking at the 2.3 source, I see a lot of changes which make me suspect that there's some legacy conventions wrt. UID/GUID etc. Like places where GUID has been replaced with UID, but the comment still saying GUID. And the new "AuthID"... Is there some where a short description of the intention of UID,GUID,shortName,AuthID ? /Peter

1 0

Is this a bug?
by Peter Mogensen 18 Aug '09

18 Aug '09

Hi, I've plugged a modified directory into DCS 1.2. It can't list records and can in principle only authenticate users. Now I'm trying to port my changes to DCS 2.2. But I find that in 2.2 twistedcaldav.directory.directory.DirectoryService.allRecords() is called. ... which is a no go, for my "directory". Looking at directory/aggregate.py I see that recordWithGUID() has been removed, so the default implementation in class DirectoryService is called. I cannot figure out from the log messages whether this was on purpose. Anyway, when there's code still calling recordWithGUID and AggregateDirectoryService doesn't implement it, it falls back to the default implementation using allRecords(), which will prevent you from plugging in a directory which cannot implement allRecords() /Peter

2 3

[CalendarServer] #345: Make iCal Server to provide subscriptions or feeds
by CalendarServer 17 Aug '09

17 Aug '09

#345: Make iCal Server to provide subscriptions or feeds -------------------------------------+-------------------------------------- Reporter: alex.thurley@… | Owner: wsanchez@… Type: Defect | Status: new Priority: 2: Expected | Milestone: CalendarServer-2.x Component: Calendar Server | Severity: Other Keywords: ICS FEED | -------------------------------------+-------------------------------------- It just happened that I got the request make our group calendar entries for 2 group calendars accessable in a website build in typo3. All calendar plugins for typo3 require an ics-file that can be read out. This should not be a problem for a calendar of an individual user that could be copied to a special place where it is then later taken to the typo3 calendar plugin, but with group calendars we've got an ics file for each event. At the moment we help us and perform a cat, e.g.: cat /Library/CalendarServer/Documents/calendars/__uids__/UID/calendar/* > /location/accessable/to/typo3.... Or does anybody know an easy way to accomplish this very simple need? Thanks! Alex -- Ticket URL: <http://trac.calendarserver.org/ticket/345> CalendarServer </> HTTP/WebDAV/CalDAV Server

1 3

[CalendarServer] #346: Exception rendering:
by CalendarServer 09 Aug '09

09 Aug '09

#346: Exception rendering: -----------------------------+---------------------------------------------- Reporter: ivan@… | Owner: wsanchez@… Type: Defect | Status: new Priority: 5: Not set | Milestone: CalendarServer-2.x Component: Calendar Server | Severity: Crash/data loss Keywords: | -----------------------------+---------------------------------------------- Hi, I installed CalendarServer this morning, everything all right. But in a crazy moment I deleted the CalendarServer folder. I download again with svn and run the server, everything OK, but when I try to access to the admin calendar whith Thunderbird+Lightning I got this error- {{{ 2009-08-05 20:10:09+0200 [-] [caldav-8009] [AMP,client] [twistedcaldav.extensions#info] HEAD /calendars/users/admin/calendar/ HTTP/1.1 2009-08-05 20:10:09+0200 [-] [caldav-8009] [PooledMemCacheProtocol,client] Exception rendering: 2009-08-05 20:10:09+0200 [-] [caldav-8009] [PooledMemCacheProtocol,client] Unhandled Error 2009-08-05 20:10:09+0200 [-] [caldav-8009] Traceback (most recent call last): 2009-08-05 20:10:09+0200 [-] [caldav-8009] File "/opt/CalServer/Twisted/twisted/internet/defer.py", line 769, in gotResult 2009-08-05 20:10:09+0200 [-] [caldav-8009] _inlineCallbacks(r, g, deferred) 2009-08-05 20:10:09+0200 [-] [caldav-8009] File "/opt/CalServer/Twisted/twisted/internet/defer.py", line 749, in _inlineCallbacks 2009-08-05 20:10:09+0200 [-] [caldav-8009] result = g.send(result) 2009-08-05 20:10:09+0200 [-] [caldav-8009] File "/opt/CalServer/CalendarServer/twistedcaldav/extensions.py", line 154, in authenticate 2009-08-05 20:10:09+0200 [-] [caldav-8009] result = (yield request.portal.login(pcreds, None, *request.loginInterfaces)) 2009-08-05 20:10:09+0200 [-] [caldav-8009] File "/opt/CalServer/Twisted/twisted/cred/portal.py", line 115, in login 2009-08-05 20:10:09+0200 [-] [caldav-8009] return maybeDeferred(self.checkers[i].requestAvatarId, credentials 2009-08-05 20:10:09+0200 [-] [caldav-8009] --- <exception caught here> --- 2009-08-05 20:10:09+0200 [-] [caldav-8009] File "/opt/CalServer/Twisted/twisted/internet/defer.py", line 104, in maybeDeferred 2009-08-05 20:10:09+0200 [-] [caldav-8009] result = f(*args, **kw) 2009-08-05 20:10:09+0200 [-] [caldav-8009] File "/opt/CalServer/CalendarServer/twistedcaldav/directory/aggregate.py", line 159, in requestAvatarId 2009-08-05 20:10:09+0200 [-] [caldav-8009] return credentials.authnPrincipal.record.service.requestAvatarId(credentials) 2009-08-05 20:10:09+0200 [-] [caldav-8009] File "/opt/CalServer/CalendarServer/twistedcaldav/directory/directory.py", line 119, in requestAvatarId 2009-08-05 20:10:09+0200 [-] [caldav-8009] return d.addCallback(_verify) 2009-08-05 20:10:09+0200 [-] [caldav-8009] exceptions.AttributeError: 'bool' object has no attribute 'addCallback' 2009-08-05 20:10:09+0200 [-] [caldav-8009] }}} I see in other tickets that this error was resolve, but why this morning CalendarServer was fine and now got a error?? Thanks. -- Ticket URL: <http://trac.calendarserver.org/ticket/346> CalendarServer </> HTTP/WebDAV/CalDAV Server

1 2

Re: [CalendarServer-dev] [CalendarServer] #260: OpenLDAP directory service
by CalendarServer 06 Aug '09

06 Aug '09

#260: OpenLDAP directory service ---------------------------------------+------------------------------------ Reporter: jusiskin@… | Owner: sagen@… Type: Feature | Status: new Priority: 2: Expected | Milestone: CalendarServer-2.x Component: Calendar Server | Severity: Other Keywords: | ---------------------------------------+------------------------------------ Comment(by rlalkaka@…): Replying to [comment:29 rahul@…]: > I have modified the patch given to me by Oxullo to include LDAP TLS support as well as filters. Also authentication is done using PAM rather than LDAP. I have only commented out the LDAP authentication code just in case you intend to revert to using LDAP server for authentication. The configuration options are as below now (I have included a sample filter option as well). Also the tlsCACertDir option does not seem to be working (no idea as to why this option is not working). I'm having some trouble getting this working. Leaving the credentials field blank (which the comments in twistedcaldav/directory/ldapdirectory.py imply will anonymously bind) prompts ./run to spew errors about the blank credentials DN (log and trace below). Is there an easy way to change the patched LDAP to bind to uid=<username>,ou=people,dc=example,dc=com and then proceed with PAM auth if the record exists, instead of searching as in the current implementation? Apologies if this is a trivial change -- I can't make head or tail of LDAP right now. {{{ [startup] Configuring directory service of type: twistedcaldav.directory.ldapdirectory.LdapDirectoryService [LdapDirectoryService] Calling ldap.initialize('ldap://ldap.server- removed.com:389/'). [-] Traceback (most recent call last): [-] File "../Twisted/bin/twistd", line 21, in ? [-] run() [-] File "/tmp/src/Twisted/twisted/scripts/twistd.py", line 27, in run [-] app.run(runApp, ServerOptions) [-] File "/tmp/src/Twisted/twisted/application/app.py", line 379, in run [-] runApp(config) [-] File "/tmp/src/Twisted/twisted/scripts/twistd.py", line 23, in runApp [-] _SomeApplicationRunner(config).run() [-] File "/tmp/src/Twisted/twisted/application/app.py", line 157, in run [-] self.application = self.createOrGetApplication() [-] File "/tmp/src/Twisted/twisted/application/app.py", line 202, in createOrGetApplication [-] ser = plg.makeService(self.config.subOptions) [-] File "/tmp/src/CalendarServer-1.2/twistedcaldav/tap.py", line 749, in makeService [-] service = serviceMethod(options) [-] File "/tmp/src/CalendarServer-1.2/twistedcaldav/tap.py", line 471, in makeService_Slave [-] baseDirectory = directoryClass(**config.DirectoryService["params"]) [-] File "/tmp/src/CalendarServer-1.2/twistedcaldav/directory/ldapdirectory.py", line 144, in __init__ [-] self._updateStorage(recordType) [-] File "/tmp/src/CalendarServer-1.2/twistedcaldav/directory/ldapdirectory.py", line 238, in _updateStorage [-] logging.info("Retrieving subtree of %s." % ldap.dn.dn2str(base), system="LdapDirectoryService") [-] AttributeError: 'module' object has no attribute 'dn' }}} -- Ticket URL: <http://trac.calendarserver.org/ticket/260#comment:31> CalendarServer </> HTTP/WebDAV/CalDAV Server

1 0

Re: [CalendarServer-dev] [CalendarServer] #260: OpenLDAP directory service
by CalendarServer 03 Aug '09

03 Aug '09

#260: OpenLDAP directory service ---------------------------------------+------------------------------------ Reporter: jusiskin@… | Owner: sagen@… Type: Feature | Status: new Priority: 2: Expected | Milestone: CalendarServer-2.x Component: Calendar Server | Severity: Other Keywords: | ---------------------------------------+------------------------------------ Comment(by rahul@…): I have modified the patch given to me by Oxullo to include LDAP TLS support as well as filters. Also authentication is done using PAM rather than LDAP. I have only commented out the LDAP authentication code just in case you intend to revert to using LDAP server for authentication. The configuration options are as below now (I have included a sample filter option as well). Also the tlsCACertDir option does not seem to be working (no idea as to why this option is not working). {{{ <key>DirectoryService</key> <dict> <key>type</key> <string>twistedcaldav.directory.ldapdirectory.LdapDirectoryService</string> <key>params</key> <dict> <key>realmName</key> <string>EXAMPLE.COM</string> <key>uri</key> <string>ldap://dbs.example.com:389/</string> <key>tls</key> <true/> <key>tlsCACertFile</key> <string>/etc/ssl/certs/dbs.example.com.pem</string> <key>tlsCACertDir</key> <string></string> <key>tlsRequireCert</key> <string>demand</string> <key>credentials</key> <dict> <key>dn</key> <string>cn=admin,dc=example,dc=com</string> <key>password</key> <string>admin123</string> </dict> <key>rdnSchema</key> <dict> <key>base</key> <string>dc=example,dc=com</string> <key>users</key> <dict> <key>rdn</key> <string>ou=People</string> <key>attr</key> <string>uid</string> <key>emailSuffix</key> <string></string> <key>filter</key> <string>(&(objectClass=x-scs-Person)(x-scs- PrivilegeName=caldav)(!(x-scs-AccountInactive=TRUE)))</string> </dict> <key>groups</key> <dict> <key>rdn</key> <string>ou=Group</string> <key>attr</key> <string>cn</string> <key>emailSuffix</key> <string></string> <key>filter</key> <string></string> </dict> <key>locations</key> <dict> <key>rdn</key> <string>ou=Locations</string> <key>attr</key> <string>cn</string> <key>emailSuffix</key> <string></string> <key>filter</key> <string></string> </dict> <key>resources</key> <dict> <key>rdn</key> <string>ou=Resources</string> <key>attr</key> <string>cn</string> <key>emailSuffix</key> <string></string> <key>filter</key> <string></string> </dict> </dict> <key>groupSchema</key> <dict> <key>membersAttr</key> <string>uniqueMember</string> <key>memberIdAttr</key> <string></string> </dict> </dict> </dict> }}} -- Ticket URL: <http://trac.calendarserver.org/ticket/260#comment:29> CalendarServer </> HTTP/WebDAV/CalDAV Server

1 0