[Users] [Bug 4762] New: oauth2: preserve an existing refresh token
noreply at thewildbeast.co.uk
noreply at thewildbeast.co.uk
Sat Feb 3 20:10:52 UTC 2024
https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4762
Bug ID: 4762
Summary: oauth2: preserve an existing refresh token
Product: Claws Mail (GTK 2)
Version: GIT
Hardware: PC
OS: All
Status: NEW
Severity: normal
Priority: P3
Component: Other
Assignee: users at lists.claws-mail.org
Reporter: olaf at aepfle.de
Created attachment 2448
-->
https://www.thewildbeast.co.uk/claws-mail/bugzilla/attachment.cgi?id=2448&action=edit
gtk2-oauth2-preserve-an-existing-refresh-token.patch
The response from the server may lack the "refresh_token". As result
->refresh_token will remain NULL. The function passwd_store_set_account will
handle NULL as "delete an existing entry". An existing, and still usable
refresh token will be removed from password store. As a result further access
to the account is blocked, until a new access and refresh token is manually
obtained in the account OAuth2 preferences.
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the Users
mailing list