You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@couchdb.apache.org by rn...@apache.org on 2020/04/27 20:12:03 UTC

[couchdb-documentation] 09/10: line wrap

This is an automated email from the ASF dual-hosted git repository.

rnewson pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/couchdb-documentation.git

commit 382d3ab3eb573d4b9cdc5e1b9c9ecae09a980c61
Author: Robert Newson <ro...@uk.ibm.com>
AuthorDate: Mon Apr 27 20:40:20 2020 +0100

    line wrap
---
 src/api/server/authn.rst | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/src/api/server/authn.rst b/src/api/server/authn.rst
index e82d404..40432fa 100644
--- a/src/api/server/authn.rst
+++ b/src/api/server/authn.rst
@@ -367,9 +367,9 @@ instead of defining users or roles in the ``_users`` database.
 The JWT authentication handler requires that all JWT tokens are signed by a key that
 CouchDB has been configured to trust (there is no support for JWT's "NONE" algorithm).
 
-Additionally, CouchDB can be configured to reject JWT tokens that are missing a
-configurable set of claims (e.g, a CouchDB administrator could insist on the ``exp``
-claim).
+Additionally, CouchDB can be configured to reject JWT tokens that are
+missing a configurable set of claims (e.g, a CouchDB administrator
+could insist on the ``exp`` claim).
 
 All claims presented in a JWT token are validated if presented, regardless of whether they
 are required.