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

Check API key button implementation #1874

Closed
6 tasks
bajiat opened this issue Nov 4, 2016 · 3 comments
Closed
6 tasks

Check API key button implementation #1874

bajiat opened this issue Nov 4, 2016 · 3 comments
Assignees

Comments

@bajiat
Copy link
Contributor

bajiat commented Nov 4, 2016

Check that the Get API key button on the API profile page works properly with Multiproxy implementation.
Note: Most of the task is probably double checking current implementation

Definition of done

  • Get API key button is only available in API profile view, if API is connected to a proxy.
  • If user presses Get API key
    • the API key comes from the connected proxy.
    • the key is updated for all APIs connected to that proxy
    • Copy API key button will be available for all APIs connected to that proxy
    • for any APIs connected to another proxy, the Get API key button is still available in the API profile view.
@jykae
Copy link
Contributor

jykae commented Nov 4, 2016

Interested

@bajiat
Copy link
Contributor Author

bajiat commented Nov 7, 2016

Consider API-specific API keys

@jykae jykae added ready and removed planning labels Nov 7, 2016
@jykae
Copy link
Contributor

jykae commented Nov 7, 2016

@bajiat As all our requests go straight to API Umbrella, API key checks are handled on API Umbrella.
I added question if it would be possible restrict the usage of API backend per API key
NREL/api-umbrella#302

I am first going for functionality defined above.

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

No branches or pull requests

3 participants