search

kidd / org-gcal.el

Org sync with Google Calendar. (active maintained project as of 2019-11-06)
432 stars 47 forks source link

oauth asking to connect to shared calendar #211

Open vnckppl opened 1 year ago

vnckppl commented 1 year ago

With the new oauth implementation, org-gcal is now treating shared calendars as accounts.

For example, if I have one email address (cal1@gmail.com) to which I share a calendar (e.g., cal2@gmail.com) my setup before the oauth implementation was:

   org-gcal-fetch-file-alist `(("cal1@gmail.com" . ,(concat syncdir "/some_file1.org"))
                               ("cal2@gmail.com" . ,(concat syncdir "/some_file2.org"))))

This worked well.

Now, when I run a sync, org-gcal tries to authenticate both cal1@gmail.com as well as cal2@gmail.com, whereas it should just treat cal2@gmail.com as a calendar that is part of cal1@gmail.com.

Because these are shared calendars, I don't necessarily own them, and thus, I cannot authenticate them.

Is it no longer possible to pull from shared calenders with the oauth implementation?

pobermei commented 1 year ago

With the latest org-gcal version a2d16b3 as of today, I can use shared calendars of which I'm not the owner of IF they are of domain @group.calendar.google.com, e.g. a calendar ID like shared-calendar@group.calendar.google.com

However, analogous to your case, I cannot use the shared primary calendar of a foreign account: e.g. for foreign account foo@gmail.com, accessing its shared primary calendar (with identical calendar ID foo@gmail.com) triggers oauth autentication for foo@gmail.com

@kidd Is there a fix/workaround for this?