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

Endpoint /api/v1/users/refresh_token generates new access token on request #6233

Open
3 tasks
7riumph opened this issue Feb 17, 2025 · 2 comments
Open
3 tasks
Labels
codethechange for codethechange developers

Comments

@7riumph
Copy link
Collaborator

7riumph commented Feb 17, 2025

Part of epic #3942

What type of user does this affect?

  • volunteers

How should it operate? ⚙️🛠️

There should now be a api/v1/users/refresh_token route to generate new access tokens (api_token).

Acceptance Criteria

  • Adds refresh_token post route to api/v1/ (/api/v1/users/refresh_token)
  • Regenerates the current api_token and replaces old api_token_digest with hashed version of new token
  • Route accepts refresh_token and returns session_blueprint data with new api_token

Helpful Links

API Folder Structure
Blueprint

@Naraveni
Copy link
Contributor

can I work on this

@7riumph
Copy link
Collaborator Author

7riumph commented Feb 28, 2025

can I work on this

Thanks for your interest, but these issues are for the Code the Change team.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
codethechange for codethechange developers
Projects
Development

No branches or pull requests

2 participants