[Users] OAUTH2 Authorisation Status

[Michael Rasmussen]

On Sat, 2 Apr 2022 09:48:08 +0100
Bernard Moreton <bernard.moreton at gmail.com> wrote:

> Has anyone managed to get a successful (ie. stable) Production
> publishing status? Changing codes every 7 days is not sustainable;
> nor is every 30 days. Google used to have a refresh code, which
> presumably would need activating on request;  but that seems to have
> dropped out of the picture ... ?
> 
You have misunderstod the problem here. You do not need to change your
password every 7 or 30 days. What you are required to do is make a new
login at the identity provider to get a new token. The token is the one
that needs to be changed and not the password. How often you need to
change the token is solely up to the identity provider.

-- 
Hilsen/Regards
Michael Rasmussen

Get my public GnuPG keys:
michael <at> rasmussen <dot> cc
https://pgp.key-server.io/pks/lookup?search=0xD3C9A00E
mir <at> datanom <dot> net
https://pgp.key-server.io/pks/lookup?search=0xE501F51C
mir <at> miras <dot> org
https://pgp.key-server.io/pks/lookup?search=0xE3E80917
--------------------------------------------------------------
/usr/games/fortune -es says:
Where there's a will, there's an Inheritance Tax.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <http://lists.claws-mail.org/pipermail/users/attachments/20220402/eab9e7eb/attachment-0001.sig>