-
Notifications
You must be signed in to change notification settings - Fork 941
Managing API keys #855
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
Managing API keys #855
Conversation
|
Your Render PR Server URL is https://superagent-pr-855.onrender.com. Follow its progress at https://dashboard.render.com/web/srv-cnepidacn0vc73ef6cn0. |
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
homanp
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@elisalimli would mind describing how you implement this? Hard for me to follow exactly what happens.
@homanp adds ability to manage API keys (JWT tokens). Previously we was offering only one API key, so people was not able to re-create or change it in any way. Now they can :) |
homanp
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
|
@homanp That's a intended decision. That API key is saved in the database. And used for all the requests over all the app. |
|
@elisalimli Good work on this! |
Fixes #853