This is an automated email from the ASF dual-hosted git repository.
rnewson pushed a change to branch jwt-enhancements
in repository https://gitbox.apache.org/repos/asf/couchdb.git.
discard 7b7370d Merge branch 'master' into jwt-enhancements
discard 1963ce9 base64 the symmetric jwt keys
discard 7a557a0 throw Reason directly so we send good http error responses
discard 23a6790 Create in-memory cache of JWT keys
discard 953c65a add EC tests
discard 6866235 support RSA for JWT auth
discard cadc0de test all variants of jwt hmac
discard bc26126 generate JWT token ourselves
discard ebe81b4 no need to deduplicate this list
add 8074a32 no need to deduplicate this list
add bb86d04 generate JWT token ourselves
add 5c77ef0 test all variants of jwt hmac
add db21eda support RSA for JWT auth
add 623ae9a add EC tests
add c1e7c5a Create in-memory cache of JWT keys
add dc88e36 throw Reason directly so we send good http error responses
add 16b3c8d base64 the symmetric jwt keys
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (7b7370d)
\
N -- N -- N refs/heads/jwt-enhancements (16b3c8d)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
No new revisions were added by this update.
Summary of changes:
