Adding JWT Authentication Functionality#1469
Open
pablodavidortega wants to merge 2 commits intoapache:mainfrom
Open
Adding JWT Authentication Functionality#1469pablodavidortega wants to merge 2 commits intoapache:mainfrom
pablodavidortega wants to merge 2 commits intoapache:mainfrom
Conversation
stopping point added tests for action loginJwt Added some more tests for the actions class JWT Token Authentication - Fixes apache#1468
pablodavidortega
force-pushed
the
jwt-auth-feature
branch
from
74d63ea to
fe64fc5
Compare
This file contains hidden or 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
1 participant
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.
Overview
CouchDB allows JWT Token authentication. FauxtonUI however, does not have a way to leverage these tokens to access the server. This change allows users to use JWT tokens as a short-lived sign on token, similar to Vault's JWT Authentication pattern. This can live side by side with an additional OIDC authentication path, similar to the one presented in #1465 .
This is implemented with a drop-down which matches the ones currently in use across the UI. Basic Auth option is kept as the default, as seen below:
The JWT option is added as a secondary option:
Testing recommendations
There are detailed instructions on how to test this feature in the file
jwt-auth.md.GitHub issue number
Fixes #1468
Related Pull Requests
Checklist