September 2013 - calendarserver-users

Problems with external invites
by Frank Keller 07 Oct '13

07 Oct '13

Dear list, we are running an OSX lion server and using caldav on it. Server: System Version: 10.7.4 (Build 11E53) Kernel: Darwin 11.4.0 Services: Mail, Open Directory, iCal Clients are running OSX 10.7.x and 10.8.x We had problems in the past with errors when refreshing calendars. It happened often that an error message 500 was shown when refreshing, especially if the user had more calendar delegations configured. After a long journey with the the apple support a workaround was mentioned to change the port from 'auto' to '8443' in the server settings for iCal on the client machines. We also changed the refresh rate for calendars from push to a fixed value. It seems that these changes solved the problems with the 500 error. Now we are facing a new error when receiving calendar invites as a attached ics file, mainly from outside our organization. When opening the attached ics file, an error 403 is shown and it is not possible to accept the invite. Contacting Apple support again was not successful because they are saying it is a different error and we need to purchase a new support case to get help from them. So the question is, can anybody give us a hint on how to solve these issue? Maybe someone already has a fix or a workaround for this error? If you need any further information, please let me know. Any help would be appreciated. Best Regards Frank

2 4

Ubuntu 12.04.3 LTS install from svn
by Gordon Turner 20 Sep '13

20 Sep '13

Morning, I am trying to build and install release CalendarServer-4.2 on a clean install of Ubuntu 12.04.3 LTS. I have been able to build and install, apparently successfully, I have summarized my process here: https://gist.github.com/gordonturner/6625260 My question is this, what is the 'approved' way of starting the server on Linux? The QuickStart () is quite clear not to use the 'run' script for init.d startup. I have tried the following, but it does not seem to start correctly, likely something I am missing: export PYTHONPATH=/usr/local/lib/python2.7:/usr/local/lib/python2.7/dist-packages /usr/local/bin/caldavd -X -f /usr/local/caldavd/caldavd.plist -T /usr/local/bin/twistd -L There are no errors, just a 'Reading configuration from file: /usr/local/caldavd/caldavd.plist' message. Any help appreciated, Gordo.

2 1

Re: [CalendarServer-users] Adding a new "role" to the Calendar Server DB?
by Andre LaBranche 17 Sep '13

17 Sep '13

Forgot to cc the list on the resolution. -dre On Sep 16, 2013, at 10:47 AM, Andre LaBranche <dre(a)apple.com> wrote: > > On Sep 14, 2013, at 9:41 PM, Scott Cherf <cherf(a)ambient-light.com> wrote: > >> Hi Andre - >> >> Thanks for the step by step guide, it all makes sense and like you I don't have postgres installed systemwide either. In my install it's in the directory above the CalendarServer (version 4.2) in CalendarServer/tags/release. Using the commands from that location gives me an error: >> >> psql: could not connect to server: No such file or directory >> Is the server running locally and accepting >> connections on Unix domain socket "/tmp/.s.PGSQL.5432"? >> >> >> The CalendarServer is running and so is postgres but the socket mentioned in the error doesn't exist. Is there a way from me to tell psql how to connect to the DB? > > Yep; that /tmp location is the default for postgres, but we stash it someplace a bit more unique. Start the service, then get a list of running postgres processes: > > ps auxww | grep -i postgres > > You should see one something like this: > > ... /Volumes/whatever/Users/andre/work/icalserver/trunk/postgresql-9.2.4/_root/bin/postgres -c listen_addresses= -k /tmp/ccs_postgres_6c305e5a2a6852bf7f384e044de707ec -c shared_buffers=49 -c max_connections=33 -c standard_conforming_strings=on > > The value after the -k switch is the path to our postgres socket file, which you can use as the value for the -h option of postgres command line tools. For example: > > andre(a)xomg[postgresql-9.2.4/_root]./bin/psql -U caldav -h /tmp/ccs_postgres_6c305e5a2a6852bf7f384e044de707ec --list > List of databases > Name | Owner | Encoding | Collate | Ctype | Access privileges > -----------+--------+----------+-------------+-------------+------------------- > caldav | caldav | UTF8 | en_US.UTF-8 | en_US.UTF-8 | > postgres | caldav | UTF8 | en_US.UTF-8 | en_US.UTF-8 | > template0 | caldav | UTF8 | en_US.UTF-8 | en_US.UTF-8 | =c/caldav + > | | | | | caldav=CTc/caldav > template1 | caldav | UTF8 | en_US.UTF-8 | en_US.UTF-8 | =c/caldav + > | | | | | caldav=CTc/caldav > (4 rows) > > HTH, > -dre > > >> >> This is a MacOS 10.6.8 installation. >> >> Regards, >> Scott. >> >> On Sep 13, 2013, at 11:30 AM, Andre LaBranche wrote: >> >>> >>> On Sep 13, 2013, at 8:26 AM, Scott Cherf <cherf(a)ambient-light.com> wrote: >>> >>>> Does anyone have a cheap trick for adding a "role" to the postgres DB CalendarServer uses? I installed the server under one user ID and wanted to move it to another but had to export the data, reinstall then import so I could run it with different permissions. There must be a simple way to just add a new role to the DB but it wasn't obvious? >>> >>> Official docs are here: http://www.postgresql.org/docs/9.2 >>> >>> It’s hard for me to predict what your exact steps would need to be, but one simple approach would be: >>> >>> * create the new user (role) in postgres >>> * grant the new user the same rights as the existing user >>> >>> Example below. Note that in this example, I don’t have postgres installed system-wide (it’s installed to ~/pg), which is why I’m saying ./bin/psql instead of just psql. YMMV. I’m also not setting any passwords for the new role; if your postgres service can be reached over the network, you may want passwords. >>> >>> # First, list the current roles. >>> >>> {38} admin@linuxbuilder [~/pg] % ./bin/psql template1 -c '\du' >>> List of roles >>> Role name | Attributes | Member of >>> -----------+------------------------------------------------+----------- >>> admin | Superuser, Create role, Create DB, Replication | {} >>> caldav | Superuser, Create role, Create DB | {} >>> >>> Let’s assume caldav is the ‘old’ account. >>> >>> >>> # Create a new role, validate it >>> >>> {39} admin@linuxbuilder [~/pg] % ./bin/createuser newman >>> {40} admin@linuxbuilder [~/pg] % ./bin/psql template1 -c '\du' >>> List of roles >>> Role name | Attributes | Member of >>> -----------+------------------------------------------------+----------- >>> admin | Superuser, Create role, Create DB, Replication | {} >>> caldav | Superuser, Create role, Create DB | {} >>> newman | | {} >>> >>> >>> # Give newman the same access as caldav, validate it. >>> >>> {41} admin@linuxbuilder [~/pg] % ./bin/psql template1 -c 'grant caldav to newman' >>> GRANT ROLE >>> {42} admin@linuxbuilder [~/pg] % ./bin/psql template1 -c '\du' >>> List of roles >>> Role name | Attributes | Member of >>> -----------+------------------------------------------------+----------- >>> admin | Superuser, Create role, Create DB, Replication | {} >>> caldav | Superuser, Create role, Create DB | {} >>> newman | | {caldav} >>> >>> Note that newman is now shown as a member of caldav. This means newman is allowed to do all the things that the caldav role can do. You don’t need to delete the caldav role. >>> >>> Also, be advised that postgres roles and permissions are not at all related to filesystem permissions or system user accounts; except that if you don’t supply a postgres username when connecting, it will pick your current system user account name as the default. >>> >>> HTH, >>> -dre >> >> Regards, >> Scott Cherf >> >> Villa Montagne Equestrian B&B >> >> 28495 Big Basin Way, >> Boulder Creek, CA >> 95006 >> >> www.villamontagne.us.com >> >

2 2

LDAP Passwords
by Thomas Reeves 17 Sep '13

17 Sep '13

Greetings Everyone! I have installed Darwin Calendar Server (DCS) v4.2 running under Centos (Linux) v6.4 using LDAP. I'm using 389 Directory Server for LDAP. Unfortunately, I can't authenticate and I suspect a password encryption issue. Specifically, userpasswd is stored in SHA1 format on my 389 Directory Server, but stored as plaintext under the default XML-based directory. My question is this: Can DCS decrypt an SHA1 format password or does it expect passwords to be in a specific format? Thanks, Thomas

2 3

Adding a new "role" to the Calendar Server DB?
by Scott Cherf 13 Sep '13

13 Sep '13

Does anyone have a cheap trick for adding a "role" to the postgres DB CalendarServer uses? I installed the server under one user ID and wanted to move it to another but had to export the data, reinstall then import so I could run it with different permissions. There must be a simple way to just add a new role to the DB but it wasn't obvious? Regards, Scott Cherf Villa Montagne Equestrian B&B 28495 Big Basin Way, Boulder Creek, CA 95006 www.villamontagne.us.com

2 1

Configuring LDAP groups and resources
by James Rowe 11 Sep '13

11 Sep '13

Hello again! The calendar server I've been installing on RHEL 6 is mostly working now, but I'm still struggling to configure the server to work with LDAP in the manner which I need. In the application that I'm writing, we have several resources that the users will be scheduling time on actual machinery and these machines are resources listed in LDAP. I took some time to read through the ConfigureLDAP article on the wiki, but now my server doesn't seem to want to load the resources properly from LDAP. First off, from what I can understand from the iCal and caldav specs is that there are 4? types of principals. Users, Groups, Resources, and Locations. Users and groups have the ability to schedule a resource at a location. Once the resource is scheduled at a certain time, no other person should be allowed to double book that resource correct? If this assumption is true then this is exactly what we need. :) So here is the difficulty I face. Using my limited understanding of LDAP and DCS I have not been able to produce a configuration file that even works right now. My goal is to pull the Users, Groups, and Resources from LDAP and the following is the path (is path the right word?) to each of these. Users - cn=users,dc=example,dc=base,dc=path Groups - groupCategory=instruments,dc=example,dc=base,dc=path (where membership in the group is defined by the memberUid attribute for each of the results returned) Resources - groupCategory=instruments,dc=example,dc=base,dc=path (where this is all of the resources) But this doesn't return any results when I try to browse to the :8008/principals/groups/ so it makes me think that I have the ldap parts improperly configured. Since I don't want the actual config to take up too much room, I have it pasted in a pastebin right here: http://pastebin.com/GnbEG0KM In summary, with my current configuration, DCS lists 0 groups and 0 resources, and I need help figuring out how to make the configuration work so that each of the instruments listed in groupCategory=instruments is both a group (with membership defined as people in the memberUid field) and each of the groupCategory=instruments is a resource. Any help is greatly appreciated! James

2 1