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
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:
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