pablodavidortega opened a new pull request, #1469:
URL: https://github.com/apache/couchdb-fauxton/pull/1469

   Some small fixes
   
   <!-- Thank you for your contribution!
   
        Please file this form by replacing the Markdown comments
        with your text. If a section needs no action - remove it.
   
        Also remember, that CouchDB uses the Review-Then-Commit (RTC) model
        of code collaboration. Positive feedback is represented +1 from 
committers
        and negative is a -1. The -1 also means veto, and needs to be addressed
        to proceed. Once there are no objections, the PR can be merged by a
        CouchDB committer.
   
        See: http://couchdb.apache.org/bylaws.html#decisions for more info. -->
   
   ## Overview
   
   <!-- Please give a short brief for the pull request,
        what problem it solves or how it makes things better. -->
   
   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](https://developer.hashicorp.com/vault/docs/auth/jwt#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:
   
   <img width="610" alt="image" 
src="https://github.com/user-attachments/assets/ebdb975e-e6a1-41af-8245-f26459ea47b7";
 />
   
   The JWT option is added as a secondary option:
   
   <img width="625" alt="image" 
src="https://github.com/user-attachments/assets/84715660-f3f6-4d0d-8169-3f19555a3dd1";
 />
   
   
   
   ## Testing recommendations
   
   There are detailed instructions on how to test this feature in the file 
`jwt-auth.md`. 
   
   <!-- Describe how we can test your changes.
        Does it provides any behaviour that the end users
        could notice? -->
   
   ## GitHub issue number
   
   Fixes #1468 
   <!-- If this is a significant change, please file a separate issue at:
        https://github.com/apache/couchdb-fauxton/issues
        and include the number here and in commit message(s) using
        syntax like "Fixes #472" or "Fixes apache/couchdb#472".  -->
   
   ## Related Pull Requests
   
   <!-- If your changes affects multiple components in different
        repositories please put links to those pull requests here.  -->
   
   ## Checklist
   
   - [X] Code is written and works correctly;
   - [X] Changes are covered by tests;
   - [X] Documentation reflects the changes;
   - [ ] Update 
[rebar.config.script](https://github.com/apache/couchdb/blob/main/rebar.config.script)
 with the correct tag once a new Fauxton release is made
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@couchdb.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to