Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

refresh_token request to /oauth/token not possible #16

Open
bratelefant opened this issue Mar 30, 2024 · 2 comments
Open

refresh_token request to /oauth/token not possible #16

bratelefant opened this issue Mar 30, 2024 · 2 comments
Labels
enhancement New feature or request

Comments

@bratelefant
Copy link

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:

  1. Setup a oauth2 according to the docs, enable debug.
  2. request an access token (eg. via postman)
  3. place a refresh token request, with a body like {refresh_token: "12345xyz", grant_type: "refresh_token"}
  4. check the logs

Expected behavior
Refresh request should provide a fresh access token

@jankapunkt jankapunkt added the enhancement New feature or request label Apr 3, 2024
@jankapunkt
Copy link
Member

Thank you @bratelefant this is indeed missing 😵 maybe I can add this in the next days

@bratelefant
Copy link
Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants