building CalDAVClientLibrary
Sorry, I must be missing something obvious. I've downloaded using svn checkout http://svn.macosforge.org/repository/calendarserver/CalDAVClientLibrary/trun... CalDAVClientLibrary. This give me a folder called CalDAVClientLibrary in my home folder (mac os 10.5.2 server). Now shouldn't I have to build something? I tried setup.py build will build the package underneath 'build/' setup.py install will install the package But those didn't get me anywhere. I'm trying to get a look at my location principal to see why it's free busy times are not showing up in the Availability window of iCal. Thanks, -- jmca
There is no setup script. Just do ./run-shell.py in the main directory to run it. -- Cyrus Daboo (Tapped out on my iPhone) On May 24, 2008, at 7:49 AM, John McAdams <johnemac@tekserve.com> wrote:
Sorry, I must be missing something obvious. I've downloaded using svn checkout http://svn.macosforge.org/repository/calendarserver/CalDAVClientLibrary/trun... CalDAVClientLibrary. This give me a folder called CalDAVClientLibrary in my home folder (mac os 10.5.2 server). Now shouldn't I have to build something?
I tried setup.py build will build the package underneath 'build/' setup.py install will install the package
But those didn't get me anywhere. I'm trying to get a look at my location principal to see why it's free busy times are not showing up in the Availability window of iCal.
Thanks, -- jmca _______________________________________________ calendarserver-users mailing list calendarserver-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/calendarserver-users
I can get the comand line util to run but the GUI build fails complaining about py2app. -Terry On May 24, 2008, at 8:47 AM, Cyrus Daboo wrote:
There is no setup script. Just do ./run-shell.py in the main directory to run it.
-- Cyrus Daboo (Tapped out on my iPhone)
On May 24, 2008, at 7:49 AM, John McAdams <johnemac@tekserve.com> wrote:
Sorry, I must be missing something obvious. I've downloaded using svn checkout http://svn.macosforge.org/repository/calendarserver/ CalDAVClientLibrary/trunk CalDAVClientLibrary. This give me a folder called CalDAVClientLibrary in my home folder (mac os 10.5.2 server). Now shouldn't I have to build something?
I tried setup.py build will build the package underneath 'build/' setup.py install will install the package
But those didn't get me anywhere. I'm trying to get a look at my location principal to see why it's free busy times are not showing up in the Availability window of iCal.
Thanks, -- jmca _______________________________________________ calendarserver-users mailing list calendarserver-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/calendarserver-users
calendarserver-users mailing list calendarserver-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/calendarserver-users
Terry Barnum digital OutPost San Diego, CA http://www.dop.com 800/464-6434
On 24 May 2008, at 23:21, Terry Barnum wrote:
I can get the comand line util to run but the GUI build fails complaining about py2app.
The first hit on Google for "py2app ical server" is: http://www.nabble.com/Re%3A-Client-library-and-admin-tool-p16311107.html If you click on the "Return to Thread:" link you will see replies dealing with the problem Scott encounters, if you also experience that yourself. Stroller.
Thank you Scott, I incorrectly assumed py2app was just the output app being built by setup.py. Now I see it's a util required to build an output app from a python script. Makes sense. Normally I'm a google-first-ask- questions-later kind of guy so I apologize for not doing that and thank you for the link. -Terry On May 25, 2008, at 8:57 AM, Stroller wrote:
On 24 May 2008, at 23:21, Terry Barnum wrote:
I can get the comand line util to run but the GUI build fails complaining about py2app.
The first hit on Google for "py2app ical server" is: http://www.nabble.com/Re%3A-Client-library-and-admin-tool- p16311107.html
If you click on the "Return to Thread:" link you will see replies dealing with the problem Scott encounters, if you also experience that yourself.
Stroller.
Terry Barnum digital OutPost San Diego, CA http://www.dop.com 800/464-6434
Hi Cyrus, The login name I was using did not have a calendar. I assigned them one and then was able to login. This is all very interesting. Seeing the files raises so many questions, but one at a time. I'm still having trouble viewing acl's. Here's some output from the command: User: diradmin Password: / > cd calendars/ /calendars > acl -i Could not retrieve DAV:acl property, status=401 /calendars > acl users/ Could not retrieve DAV:acl property, status=401 /calendars > ls groups/ locations/ resources/ sudoers/ users/ /calendars > acl users Could not retrieve DAV:acl property, status=401 /calendars > Best regards, -- jmca On May 24, 2008, at 11:47 AM, Cyrus Daboo wrote:
There is no setup script. Just do ./run-shell.py in the main directory to run it.
-- Cyrus Daboo (Tapped out on my iPhone)
On May 24, 2008, at 7:49 AM, John McAdams <johnemac@tekserve.com> wrote:
Sorry, I must be missing something obvious. I've downloaded using svn checkout http://svn.macosforge.org/repository/calendarserver/CalDAVClientLibrary/trun... CalDAVClientLibrary. This give me a folder called CalDAVClientLibrary in my home folder (mac os 10.5.2 server). Now shouldn't I have to build something?
I tried setup.py build will build the package underneath 'build/' setup.py install will install the package
But those didn't get me anywhere. I'm trying to get a look at my location principal to see why it's free busy times are not showing up in the Availability window of iCal.
Thanks, -- jmca _______________________________________________ calendarserver-users mailing list calendarserver-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/calendarserver-users
Hi Cyrus, The login name I was using did not have a calendar. I assigned them one and then was able to login. However I'm still having trouble viewing acl's. Here's some output from the command: User: diradmin Password: / > cd calendars/ /calendars > acl -i Could not retrieve DAV:acl property, status=401 /calendars > acl users/ Could not retrieve DAV:acl property, status=401 /calendars > ls groups/ locations/ resources/ sudoers/ users/ /calendars > acl users Could not retrieve DAV:acl property, status=401 /calendars > On May 24, 2008, at 11:47 AM, Cyrus Daboo wrote:
There is no setup script. Just do ./run-shell.py in the main directory to run it.
-- Cyrus Daboo (Tapped out on my iPhone)
On May 24, 2008, at 7:49 AM, John McAdams <johnemac@tekserve.com> wrote:
Sorry, I must be missing something obvious. I've downloaded using svn checkout http://svn.macosforge.org/repository/calendarserver/CalDAVClientLibrary/trun... CalDAVClientLibrary. This give me a folder called CalDAVClientLibrary in my home folder (mac os 10.5.2 server). Now shouldn't I have to build something?
I tried setup.py build will build the package underneath 'build/' setup.py install will install the package
But those didn't get me anywhere. I'm trying to get a look at my location principal to see why it's free busy times are not showing up in the Availability window of iCal.
Thanks, -- jmca _______________________________________________ calendarserver-users mailing list calendarserver-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/calendarserver-users
Hi John, --On May 26, 2008 3:28:06 PM -0400 John McAdams <johnemac@tekserve.com> wrote:
I'm still having trouble viewing acl's. Here's some output from the command:
User: diradmin Password: / > cd calendars/ /calendars > acl -i Could not retrieve DAV:acl property, status=401 /calendars > acl users/ Could not retrieve DAV:acl property, status=401 /calendars > ls groups/ locations/ resources/ sudoers/ users/ /calendars > acl users Could not retrieve DAV:acl property, status=401 /calendars >
A 401 means unauthenticated. Are you sure that the "diradmin" user is properly setup for use with the calendar server? -- Cyrus Daboo
Hi Cyrus, On May 27, 2008, at 10:03 AM, Cyrus Daboo wrote:
Hi John,
A 401 means unauthenticated. Are you sure that the "diradmin" user is properly setup for use with the calendar server?
I can add the diradmin account in iCal and create events, invite people to things and what not. Is there another level of authentication the user needs to manipulate acl's? The same error has come up using other names. Best, -- jmca
Hi John, --On May 27, 2008 12:14:03 PM -0400 John McAdams <johnemac@tekserve.com> wrote:
A 401 means unauthenticated. Are you sure that the "diradmin" user is properly setup for use with the calendar server?
I can add the diradmin account in iCal and create events, invite people to things and what not. Is there another level of authentication the user needs to manipulate acl's? The same error has come up using other names.
OK - regular users can only access ACLs on their own calendar "home" collection (and anything within it): e.g. /calendars/users/diradmin. If you configure an admin user in the caldavd.plist file, that user will be able to read (and set) ACLs on any resource. -- Cyrus Daboo
Hi Cyrus, Sorry this is still giving me problems. I modified the caldavd.plist and restarted iCal Server. I'm still getting the 401 error. Here's the entry in caldavd.plist: <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd "> <plist version="1.0"> <dict> <key>AccessLogFile</key> <string>/var/log/caldavd/access.log</string> <key>AdminPrincipals</key> <array> <string>/principals/users/diradmin</string> </array> I also tried: <key>AdminPrincipals</key> <array> <string>/principals/__uids__/912F0CD3-1984-47B8-B09E-25F2BEA9DF02</ string> </array> Thanks, -- jmca On May 27, 2008, at 12:17 PM, Cyrus Daboo wrote:
Hi John,
--On May 27, 2008 12:14:03 PM -0400 John McAdams <johnemac@tekserve.com
wrote:
A 401 means unauthenticated. Are you sure that the "diradmin" user is properly setup for use with the calendar server?
I can add the diradmin account in iCal and create events, invite people to things and what not. Is there another level of authentication the user needs to manipulate acl's? The same error has come up using other names.
OK - regular users can only access ACLs on their own calendar "home" collection (and anything within it): e.g. /calendars/users/diradmin.
If you configure an admin user in the caldavd.plist file, that user will be able to read (and set) ACLs on any resource.
-- Cyrus Daboo
I've also run into the problem of the admin I set in caldavd.plist not really being an admin. The way I worked around it is I used the command line client to log in as each user and set the ACL's I wanted that way. That wasn't so bad (we're a small shop). But I could see it being a lot to do if you're serving a larger group. Cheers, tack On May 29, 2008, at 5:28 AM, John McAdams wrote:
Hi Cyrus,
Sorry this is still giving me problems. I modified the caldavd.plist and restarted iCal Server. I'm still getting the 401 error. Here's the entry in caldavd.plist:
<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd "> <plist version="1.0"> <dict> <key>AccessLogFile</key> <string>/var/log/caldavd/access.log</string> <key>AdminPrincipals</key> <array> <string>/principals/users/diradmin</string> </array>
I also tried:
<key>AdminPrincipals</key> <array> <string>/principals/__uids__/912F0CD3-1984-47B8-B09E-25F2BEA9DF02</ string> </array>
Thanks, -- jmca
On May 27, 2008, at 12:17 PM, Cyrus Daboo wrote:
Hi John,
--On May 27, 2008 12:14:03 PM -0400 John McAdams <johnemac@tekserve.com
wrote:
A 401 means unauthenticated. Are you sure that the "diradmin" user is properly setup for use with the calendar server?
I can add the diradmin account in iCal and create events, invite people to things and what not. Is there another level of authentication the user needs to manipulate acl's? The same error has come up using other names.
OK - regular users can only access ACLs on their own calendar "home" collection (and anything within it): e.g. /calendars/users/ diradmin.
If you configure an admin user in the caldavd.plist file, that user will be able to read (and set) ACLs on any resource.
-- Cyrus Daboo
_______________________________________________ calendarserver-users mailing list calendarserver-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/calendarserver-users
Hi tack, --On May 29, 2008 10:24:14 AM -0700 tack <tack@tractionco.com> wrote:
I've also run into the problem of the admin I set in caldavd.plist not really being an admin. The way I worked around it is I used the command line client to log in as each user and set the ACL's I wanted that way. That wasn't so bad (we're a small shop). But I could see it being a lot to do if you're serving a larger group.
The admin principal set in the .plist must be specified using the /principals/__uids__/<<guid>> form of the principal URL. Was that what you used? -- Cyrus Daboo
I tried that and many other things. We just upgraded to the most recent stable release though and I haven't hopped in it yet. I'll try again and see what happens. Cheers, tack On May 29, 2008, at 10:26 AM, Cyrus Daboo wrote:
Hi tack,
--On May 29, 2008 10:24:14 AM -0700 tack <tack@tractionco.com> wrote:
I've also run into the problem of the admin I set in caldavd.plist not really being an admin. The way I worked around it is I used the command line client to log in as each user and set the ACL's I wanted that way. That wasn't so bad (we're a small shop). But I could see it being a lot to do if you're serving a larger group.
The admin principal set in the .plist must be specified using the / principals/__uids__/<<guid>> form of the principal URL. Was that what you used?
-- Cyrus Daboo
Got proper admin working. Turns out this wasn't a problem with calendar server itself. It's default config is to use caldavd- dev.plist instead of caldavd.plist: config="${wd}/conf/caldavd-dev.plist"; Another admin here installed the app and I configured it, so I wasn't intimate with the install/run process. I was hacking on caldavd.plist and accounts.xml. Which makes sense: If your background is configuring apache, samba, asterisk and other such services, you haven't come across things like -dev or -test as default config options. I went to what I thought were the 'real' config files. I'm sure that the DCS team had a good reason for setting things up the way they did, so I won't harp on that point. What I will say is that I DID "read the f* manual" and it didn't help me learn the nature of the default configs. So I'd chalk this up as a documentation snafu. Cheers, tack On May 29, 2008, at 10:26 AM, Cyrus Daboo wrote:
Hi tack,
--On May 29, 2008 10:24:14 AM -0700 tack <tack@tractionco.com> wrote:
I've also run into the problem of the admin I set in caldavd.plist not really being an admin. The way I worked around it is I used the command line client to log in as each user and set the ACL's I wanted that way. That wasn't so bad (we're a small shop). But I could see it being a lot to do if you're serving a larger group.
The admin principal set in the .plist must be specified using the / principals/__uids__/<<guid>> form of the principal URL. Was that what you used?
-- Cyrus Daboo
participants (5)
-
Cyrus Daboo
-
John McAdams
-
Stroller
-
tack
-
Terry Barnum