Improved API keys logic

[dmytrotsko]

Prerequisites:

• Unless it is a documentation hotfix it should be merged against the dev branch
• Branch is up-to-date with the branch to be merged with, i.e. dev
• Build is successful
• Code is cleaned up and formatted (Black was used as a code formatter)

Summary

Implements the server logic to require API keys and roles for the endpoints.

List of tasks:

• check for api key
• show a soft warning
• show a hard warning
• adapt tests
• admin interface
• [?] log / track api_key + query if allowed
• create basic google form
• connect google form with api server handling -> webhook
• create a basic request a key form: /admin/create_key
• use flask-limited for rate limiting
• setup a Redis DB for shared rate limit tracking
• add email address validation
• fix logging (for now we are logging user requests with api_key even without asking user wether he wants to be logged)
• update documentation ???
• add tests for admin endpoint
• define a good default rate limit
• consider using Redis DB also for account management instead of SQL server

[krivard]

@dmytrotsko do you need to add a redis image to Makefile and ci.yaml?

[dmytrotsko]

@dmytrotsko do you need to add a redis image to Makefile and ci.yaml?

I'm not sure actually about ci.yaml.
But I think I can add it to Makefile as we need it to be built to use API keys stuff.
Or if we have Redis instance somewhere else we just need to provide it in env variables for web-server start.

[krivard]

If we need a redis server in order to pass integration tests, then we need to set one up in ci.yaml

[krivard]

(this PR is not currently running integration tests since it was made from a fork)

[dmytrotsko]

If we need a redis server in order to pass integration tests, then we need to set one up in ci.yaml

Okay. I see. Will add it to ci.yaml then

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication

[github-advanced-security]

You have successfully added a new SonarCloud configuration ``. As part of the setup process, we have scanned this repository and found no existing alerts. In the future, you will see all code scanning alerts on the repository Security tab.