-
Notifications
You must be signed in to change notification settings - Fork 5
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
General API Keys #124
General API Keys #124
Conversation
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.
Great start I think. Is there an API keys spec? I think the current format is quite loose? It doesn't really consider future extensions, like permissions for example. Should we think about stuff like that already? I don't mind it being loosely defined, I'm just asking.
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.
Generally lgtm
This is the spec: https://hackmd.io/tB6WDA73Q7iQGSFTqinVZg My intention was to get the simple case going first and then build on top of it. We agreed that there won't be any permissions for the moment, as that would expand the scope a lot. We want to have the so-called "sponsor" api keys which allow anyone to download a skylink with the owner of the api key paying for the traffic. I see those as a separate PR because there will be quite some code around them as well and I don't want this to be a 2000 lines PR. I'd rather iterate over the idea in 2, 3, even 5 PRs. |
userLimitsGET returns anonymous limits and logs an error if the given API key is not valid. Endpoints renamed from `/user/apikey` to `/user/apikeys`. testAPIKeysUsage now validates user stats values.
…t the `db` prefix.
Change the DELETE endpoint to work by ID.
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.
Approved with some f/u comments.
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.
LGTM, but we should def. make sure to F/U with all of the F/U's
PULL REQUEST
Overview
This PR implements the generic version of API keys:
Example for Visual Changes
Checklist
Review and complete the checklist to ensure that the PR is complete before assigned to an approver.
Issues Closed