README: explain publishing the OAuth app and logging in again

This commit is contained in:
Daniele Fucini committed 2026-11-21 16:01:38 +01:00
1 parent a186da6cfd
commit 1aa36684b6
1 file changed
+10 -2
+10 -2
View File
@@ -64,5 +64,13 @@ and `--suffix` change the defaults (Dracula pink and cyan, a Nerd Font calendar
## Login expiry ## Login expiry
With the OAuth client's consent screen in "Testing" status, Google expires the login after 7 days; in "In With the OAuth client's consent screen in "Testing" status, Google documents a 7-day login expiry. Publishing it
production" (no verification needed for your own account) it lasts until revoked or unused for 6 months. ("In production") makes the login last until revoked or unused for 6 months. Publishing needs no verification for
personal use (the login shows an "unverified app" warning once), but the Branding page needs an app home page and a
privacy policy URL on an authorized domain, besides the starred fields. After publishing, log in again: logins
issued while in Testing may keep the limit.
```
mv ~/.config/calcurse/caldav/oauth2_cred ~/.config/calcurse/caldav/oauth2_cred.bak
calcurse-relogin
```