Hi, I've been playing around with the calendar api, and I've hit the 'authsub doesn't work for google domains' issue. It seems to me that a possible workaround to this is to have the user share the calendar with a google account (domain or otherwise) that your service uses for api access - i.e. rather than have the user follow the normal authsub process, or have them hand over their domain account password, they go to 'manage calendars', and share the calendar with the appropriate level of access with [EMAIL PROTECTED] (or any e-mail address with a google account). This also gives them a finer grained access control than authsub would - the service can only see the individual calendar(s) which are shared, rather than getting access to all of them.
What I don't know, is whether this would really scale - could a single google account have access to thousands of different calendars? When you share a calendar, it's automatically added to the list of calendars for that account, so you can easily find the users calendar (and then maybe delete it from the list, to stop the list getting too long?). Or you could have the user give you the url of their calendar after they have shared it. I've tried these things with one or two calendars, and it seems to work nicely. Does this approach sound like it would work/scale? Or is 'authsub for google domains' coming soon? Have fun, Rich --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Calendar Data API" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/google-calendar-help-dataapi?hl=en -~----------~----~----~----~------~----~------~--~---
