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

Access key authentication #218

Closed
chaoran-chen opened this issue Apr 5, 2023 · 0 comments · Fixed by #238 or #778
Closed

Access key authentication #218

chaoran-chen opened this issue Apr 5, 2023 · 0 comments · Fixed by #238 or #778
Assignees
Labels
LAPIS Tasks/PR related to LAPIS
Milestone

Comments

@chaoran-chen
Copy link
Member

chaoran-chen commented Apr 5, 2023

For non-open instances such as the GISAID one, we only allow access if an access key is provided.

  • It should be possible to specify the data openness level in the config. There should be two openness levels: open and gisaid.
  • If the openness level is gisaid, the server should only allow access with a valid access key. In the current LAPIS, the access keys are stored in the PostgreSQL database. As we probably won't have an external relational database in LAPIS v2, we can also just keep them in a file.
@chaoran-chen chaoran-chen added the LAPIS Tasks/PR related to LAPIS label Apr 5, 2023
@chaoran-chen chaoran-chen added this to the COVID-LAPIS milestone Apr 5, 2023
@fengelniederhammer fengelniederhammer self-assigned this Apr 13, 2023
@fengelniederhammer fengelniederhammer linked a pull request Apr 25, 2023 that will close this issue
fengelniederhammer added a commit that referenced this issue May 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
LAPIS Tasks/PR related to LAPIS
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants