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

[FEATURE] API keys #32

Open
akulmehta opened this issue Jul 14, 2021 · 0 comments
Open

[FEATURE] API keys #32

akulmehta opened this issue Jul 14, 2021 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@akulmehta
Copy link
Collaborator

Is your feature request related to a problem? Please describe.
Entering data currently requires authentication step before calling separate api to submit/retrieve data. It would be nice to have api keys as a way of eliminating the step.

Potential reasons:

  • Efficiency: Fewer requests would need to be made hopefully speeding up data submissions especially when doing in bulk.
  • Maintainability: Imagine a scenario where I set username and password in my environment variables and then use that to authenticate. However, someone uses the front end of the repository to deposit the data for our group and goes and resets the password. Now since the current system is tightly coupled to username and password, the application would break unless I go in the code and change the username and password.

Describe the solution you'd like
Have public key and private key to authorize applications for submitting/retrieving data.

Page
https://glygen.ccrc.uga.edu/ggarray/api/swagger-ui.html

@akulmehta akulmehta added the enhancement New feature or request label Jul 14, 2021
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