From 1aa36684b64bea962ea8a8d2fc1abc45f18c4edf Mon Sep 17 00:00:00 2001 From: Daniele Fucini Date: Sat, 21 Nov 2026 16:01:38 +0100 Subject: [PATCH] README: explain publishing the OAuth app and logging in again --- README.md | 12 ++++++++++-- 1 file changed, 10 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 627a6f1..15c40a3 100644 --- a/README.md +++ b/README.md @@ -64,5 +64,13 @@ and `--suffix` change the defaults (Dracula pink and cyan, a Nerd Font calendar ## Login expiry -With the OAuth client's consent screen in "Testing" status, Google expires the login after 7 days; in "In -production" (no verification needed for your own account) it lasts until revoked or unused for 6 months. +With the OAuth client's consent screen in "Testing" status, Google documents a 7-day login expiry. Publishing it +("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 +```