[CalendarServer-users] CalDAVClientLibrary Kerberos authentication

Ramon Ziai rziai at sfs.uni-tuebingen.de
Fri Apr 17 07:15:59 PDT 2009

Hi caldavd users,

I was looking for a way to manage ACLs on individual calendars and came
across CalDAVClientLibrary. I assume that's the recommended way of
managing ACLs, is that correct?

However, it seems CalDAVClientLibrary does not support Kerberos
authentication. Our caldavd installation runs on Debian Lenny, using the
Debian package. It is configured to use Kerberos for authentication,
which works well with all calendar clients. But when I run the shell
tool, I get:

./runshell.py -l --server https://server:8443
User: rziai

        <-------- BEGIN HTTP CONNECTION -------->
Server: limnos

        <-------- BEGIN HTTP REQUEST -------->
OPTIONS /principals/users/rziai/ HTTP/1.1
Host: limnos

        <-------- BEGIN HTTP RESPONSE -------->
HTTP/1.1 401 Unauthorized
Content-Length: 141
Server: Twisted/8.1.0 TwistedWeb/[twisted.web2, version 0.2.0]
DAV: 1, access-control, calendar-access, calendar-schedule,
calendar-availability, inbox-availability, calendar-proxy
Date: Fri, 17 Apr 2009 14:11:26 GMT
Content-Type: text/html
WWW-Authenticate: negotiate
are not authorized to access this resource.</p></body></html>
        <-------- END HTTP RESPONSE -------->

        <-------- END HTTP CONNECTION -------->
Ignoring error

If it supported Kerberos, it shouldn't even ask for a password and
instead just use the ticket I already have in my ticket cache.

Any hints would be appreciated.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 260 bytes
Desc: OpenPGP digital signature
URL: <http://lists.macosforge.org/pipermail/calendarserver-users/attachments/20090417/6b661759/attachment.bin>

More information about the calendarserver-users mailing list