README: explain publishing the OAuth app and logging in again
This commit is contained in:
1 file changed
+10
-2
@@ -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
|
||||
```
|
||||
Reference in new issue
Block a user