feat: token authentication for api access; fix #44 #47
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This Pr adds the feature of validating an OAuth/OIDC access token in the
Authorization
header for authentication. First the presence of a token is checked, then its validity. In case of failure, the original basic auth check is performed. At the moment, I tested it with Keycloak as the Identity Provider and RS256 signed tokens and the public keys that are exposed by keyloack under/protocol/openid-connect/certs