Feature/SK-721 | Add JWT verification (decoding) #543
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Adds authentication decorators using JWT. Introducing RBAC with custom claims "role" in issued tokens. Current roles are:
If env FEDN_JWT_SECRET_KEY is set, JWT verification are enabled.
Custom claims can be added by setting FEDN_JWT_CUSTOM_CLAIM_KEY and verified against FEDN_JWT_CUSTOM_CLAIM_VALUE.
FEDN_AUTH_SCHEME, default to "Token".
OBS that FEDn do not issue the tokens.