You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
According to RFC 6749, a refresh of an access token only requires the grant_type and the refresh_token. However, an incoming request fails with the message [validation error]: key <code> => expected <[object Object]>, got <undefined>.
To Reproduce
Steps to reproduce the behavior:
Setup a oauth2 according to the docs, enable debug.
request an access token (eg. via postman)
place a refresh token request, with a body like {refresh_token: "12345xyz", grant_type: "refresh_token"}
check the logs
Expected behavior
Refresh request should provide a fresh access token
The text was updated successfully, but these errors were encountered:
I already did some work on this on a local copy, maybe if we can fix #17 I could contribute a PR. Ran across several other issues and possible improvements (eg. implement a meteor 3.0 compatible model). Would also really like to address this enhancement.
Describe the bug
According to RFC 6749, a refresh of an access token only requires the grant_type and the refresh_token. However, an incoming request fails with the message
[validation error]: key <code> => expected <[object Object]>, got <undefined>
.To Reproduce
Steps to reproduce the behavior:
refresh token
request, with a body like{refresh_token: "12345xyz", grant_type: "refresh_token"}
Expected behavior
Refresh request should provide a fresh access token
The text was updated successfully, but these errors were encountered: