Re: [CalendarServer-users] Problem creating multiple calendars for the same user
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 22/06/12 11:44, Glyph wrote:
Le Jun 21, 2012 à 4:40 PM, Jane Atkinson <jea62q@xtra.co.nz> a écrit :
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 22/06/12 02:16, Cyrus Daboo wrote:
Hi Jane,
--On June 21, 2012 9:52:18 PM +1200 Jane Atkinson <jea62q@xtra.co.nz> wrote:
If you can set up Calendar Server 3.0+, I'd be happy to help you diagnose the bad 'create' behavior on the part of these clients. But, for all I know, it's a bug in the old version of calendar server, and when you try a newer version, it might just work.
I've installed calendarserver 3.2 (from the repo) on Ubuntu 12.10, and I'm still having the same problem. I.e. I can create the default calendar without difficulty, but other calendars don't work.
I've just been using the default "admin" account for testing; I've made no changes to any config files. Maybe there is further setting up that needs to be done.
Calendars are not automatically created beyond the very first one when a user first accesses their account.
To create a calendar a client must use an HTTP request. If your clients do not offer a way to do that for CalDAV accounts, then they are arguably deficient. You can use the curl command to create a new calendar like this:
curl -X MKCALENDAR -u user01 https://yourhost:8443/calendars/users/user01/newcalendar/
where 'user01' is the user id of the person who is creating the calendar. The command will prompt for a password. Make sure you include a trailing slash on the end of the URI.
Thanks for the suggestion. Unfortunately, the command failed.
curl -X MKCALENDAR -u admin http://192.168.1.67:8008/calendars/users/admin/newcalendar/ Enter host password for user 'admin': <html><head><title>Unauthorized</title></head><body><h1>Unauthorized</h1><p>You
are not authorized to access this resource.</p></body></html>
(Yes, the command was all on one line; the email wrapped it. And I don't have https set up yet - should that make a difference?)
Sorry if this is a silly question, but, are you sure you typed your admin password properly? This just looks like your authentication failed. (Again: any interesting messages in the error log?)
-glyph
Not a silly question at all. It happens. :) However, in this case, the log revealed that basic authentication hadn't been set. Once I'd done that, the command went through and the new directory is listed in the web interface. Jane -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJP47qlAAoJEERzSJEx033jU0wH/34u3piCVWRaKbW1ytfBQT6y kOVq2DZNtq4osiLLCg8RfyOCx8F/oZyRggTzJVNzbsD8anx1w5Y6yT6QgHUrfJoC eU7PaEPULp2By60kFB2Hjh2mjNPk2ZhrBUMkBp9i2jcUEQZ2EnMQkzAZFhsFokVs CoZyF8zt4W9VBjZaAUbgLN8qapBMwXsL4gYklqeV7Q4XaInrghyuJcuTKC/nULWk 8jaDDyiYGYIKxta2VBoZNAvJ5SmK3dTbJ385ddlXVJ4lAgzwjadKMD9nHNu9Koly n+q2SO1IHWoqfiSc7q2gQ27AKrdUEwPzzywrwpQTK5/SD9oiKU7nG3NUGV6qNZQ= =js3w -----END PGP SIGNATURE-----
participants (1)
-
Jane Atkinson