Hi Team. The documentation does not advise a key feature/capability required for authN/authZ. If you improve and clarify your docs around this process, you could close multiple open issues and prevent a lot of developer heartache.
Problem/Issue
ZERO documentation on how to refresh a users OIDC id_token or OAuth access_token before the 1 hour expiry. This method, that can be used to accomplish authN/authZ refresh, doesn't mention anything about the fact that it automatically fires near token expiry, or can be used to refresh a users credentials.
Documentation to update
Related OPEN issues
https://github.com/google/google-api-javascript-client/issues/643
https://github.com/google/google-api-javascript-client/issues/599
https://github.com/google/google-api-javascript-client/issues/626
https://github.com/google/google-api-javascript-client/issues/469
https://github.com/google/google-api-javascript-client/issues/382
This is very much needed - the documentation only shows the login once example and is missing the important point: How to keep the user conveniently and securely logged in? What is the "secure storage" mentioned here in the OAuth docs - 5. Refresh the access token, if necessary. ?
+1
Most helpful comment
This is very much needed - the documentation only shows the login once example and is missing the important point: How to keep the user conveniently and securely logged in? What is the "secure storage" mentioned here in the OAuth docs - 5. Refresh the access token, if necessary. ?