Add callback-function for authorization #173
Description
@quaat @CasperWA @francescalb @Treesarj @jesper-friis @kriwiik
Since we are currently working on the deployment of the oteapi-services (and the remaining OTE-components such as the ESS, OntoKB, etc.), we previously also addressed the need of an authorization layer within the OTE-services. @quaat argued to go straight forward with a keycloak-container within the docker-compose network.
Since we are already applying very similar solutions in the MarketPlace, a simple OAuth2Session might be sufficient, which is wrapping around the functions for the routes of the OTE-services and which is receiving the bearer-tokens from the request-headers .
However, it might be handy that the authorization layer is optional for testing purposes and but could be enabled for deployment when the callback-url is supported in the env-variables of the docker-compose.yml.
I am curious about your opintions and anwsers!