![Thunderbird logo](https://assets-prod.sumo.prod.webservices.mozgcp.net/media/uploads/products/2024-02-12-07-36-53-599028_1.png)
Cannot add OAuth2 Google calendar on custom domain
I have a custom domain (me@mydomain.com) with email / contacts / calendar hosted by Google Workspace. I initially managed to add both the email and calendar account to Thunderbird but recently the calendar stopped syncing.
I tried to fix the problem by first removing the calendar account. This did not work because the 'Create New Calendar' -> 'On the Network' account wizard does not prompt me for the Google OAuth2 login page but just asks me for a password and fails. I tried to supply several 'Location:' URLs like gmail.com, calendar/accounts.google.com but none lead to the Google OAuth2 page.
Finally I removed the email account too and re-added it. During the new account setup workflow Thunderbird seems to look for calendars too but failed to find any...
How do I proceed? How are you supposed to set up a Google Calendar on a custom domain using the OAuth2 sign-in procedure?
所有回覆 (2)
Google have a "landing" page for caldav. https://apidata.googleusercontent.com/caldav/v2/calid/user or perhaps the default location Thunderbird supplies when you type in a google email address of google.com may suffice to set it to auth and detect the calendars when authorised
See Googles documentation for caldav here https://developers.google.com/calendar/caldav/v2/guide
Thank you for your answer. It wasn't straightforward but I eventually figured it out.
For future reference: - Add New Calendar 'On the Network' - Username: The part of your email address before the @. (E.g. username 'me' for me@mydomain.com) - Location: https://apidata.googleusercontent.com/caldav/v2/CALID/user Where CALID is to be replaced by your Calendar ID, in my case it was my full email: https://apidata.googleusercontent.com/caldav/v2/me@mydomain.com/user
Thunderbird then prompted me with the OAuth2 login page and calendar discovery was straight forward from there.
This should be fixed by Mozilla to be more user friendly / documented. Could be easily resolved by offering a calendar provider dropdown or even easier, allow user initiated calendar discovery via already existing email accounts.