Repository navigation
Please improve the documentation around refreshing authorization #140
Description
Activity
I created a pull request with proposed update. I suggest we continue our discussion there if needed.
Reopening, we need to provide a sample for non-auto access token refreshing.
In the absence of the refresh_token the application must do the OAuth flow again; however, this time, there is no user consent screen present and the returned authorisation code can be exchanged for access_token.
Would it be sufficient to include a similar description on this topic in the README? It seems that the process is mostly the same otherwise.
We presume that the developer is already familiar with OAuth 2.0 flows before using the lib, but it's not the reality at all times.
We don't need to OAuth 2.0 again, I agree that a link should be sufficient enough.
Perhaps it is me but I can't really understand what you mean in the documentation when you write:
it asks... who is "it"? Who needs to replay the request?
I hoped that the conversations around issue #14 and #42 could reveal what was missing, but they don't, and I still don't get how we are supposed to use the refresh_token. Moreover, there are references to a wiki that you probably closed since then.
The example referenced in the documentation also does not cover the refresh scenario.
Thank you in advance for any hint.
Giacecco