Google Refresh token rule is incorrect
See original GitHub issuehttps://github.com/auth0/rules/blob/master/rules/google-refresh-token.md
is wrong. refresh_token
is stored in the identities
array. It can be retrieved like the access_token
Issue Analytics
- State:
- Created 7 years ago
- Comments:8 (1 by maintainers)
Top Results From Across the Web
Access Token and Refresh token giving invalid grant in ...
When the number of refresh tokens exceeds the limit, older tokens become invalid. If the application attempts to use an invalidated refresh ...
Read more >How to figure out why refresh token become invalid or ...
The problem I am facing is some refresh token will become invalid/expired after one day randomly. Error message is Error:"invalid_grant", ...
Read more >Solved: Error message while for invalid refersh token? - Apigee
The following FaultRule works -- and your AssignMessage is called as expected when an invalid refresh token comes in. If you can't get...
Read more >Common Errors - Ads API
Your Google project's publishing status is Testing so the refresh token expires every 7 days and receives an invalid_grant error. Go to the...
Read more >Google OAuth “invalid_grant” nightmare — and how to fix it
The provided authorization grant (e.g., authorization code, resource owner credentials) or refresh token is invalid, expired, revoked, does not match the ...
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
@mtt87 You where totally right.
scope: offline_access
andaccess_type: offline
are different options. Finally I’ve just added to my request following line:It helped and now after log in user.identities contains google refresh token. Thanks a lot! You helped me to solve issue, I was working with for long time.
I think I’ve spotted the problem it’s not
scope: offline_access
but it’s an additional parameteraccess_type: offline
This is an example of what I’m doing, I hope it helps.
lock
that I use on my webappPOST /users
to create the new user with{ userId: xxx, userEmail: yyy }
, then the server is making a request usingmanagement API
to retrieve the user. See that there is no scope or stuff like that, it’s just a plain call.