« Return to Thread: CalDAVClientLibrary Kerberos authentication
CalDAVClientLibrary Kerberos authentication
by Ramon Ziai
::
Rate this Message:
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
Password:
<-------- 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
<html><head><title>Unauthorized</title></head><body><h1>Unauthorized</h1><p>You
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.
Best,
Ramon
_______________________________________________
calendarserver-users mailing list
calendarserver-users@...
http://lists.macosforge.org/mailman/listinfo.cgi/calendarserver-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
Password:
<-------- 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
<html><head><title>Unauthorized</title></head><body><h1>Unauthorized</h1><p>You
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.
Best,
Ramon
_______________________________________________
calendarserver-users mailing list
calendarserver-users@...
http://lists.macosforge.org/mailman/listinfo.cgi/calendarserver-users
signature.asc (268 bytes) « Return to Thread: CalDAVClientLibrary Kerberos authentication
| Free embeddable forum powered by Nabble | Forum Help |
