Wrong function name in refresh token documentation
See original GitHub issueDescribe the bug Documentation improvement
To Reproduce Steps to reproduce the behavior:
Expected behavior The function name refrenced in the documentation should match the name in the code
Additional context
In the document the function name for refreshing a token seems to be wrong
this.oauthService.refresh();
I think it should be:
this.oauthService.refreshToken();
Issue Analytics
- State:
- Created 3 years ago
- Comments:5
Top Results From Across the Web
Understanding Refresh Tokens - Auth0
Using Refresh Tokens While refresh tokens are often long-lived, the authorization server can invalidate them. Some of the reasons a refresh token may...
Read more >Refresh Tokens - OAuth 2.0 Simplified
The presence of the refresh token means that the access token will expire and you'll be able to get a new one without...
Read more >Re: Access token expired in V3 - Constant Contact Community
If you continue going through the oAuth documentation for v3 you will notice that it mentions a Refresh Token section after the Access...
Read more >Troubleshooting | CyberDrain Improved Partner Portal
Reset the token names to their original values, for example back to RefreshToken and then Select Save. Stop the app once more for...
Read more >Solved: OAuth Refresh token has expired after 90 days
We try to authenticate using an OAuth Refresh Token (this authentication mechanism has ... In this case the documentation is wrong and should...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
pinging to notify this can be closed (if forgotten)
Thx!
Note that it’s typically the core maintainer to merge a bunch of PRs at once, every once in a while, so it might take a bit.