From 5c5d71cce917b09ae6583be90c6441e538ee8e44 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Douglas=20Mendiz=C3=A1bal?= Date: Tue, 14 May 2019 11:32:11 -0500 Subject: [PATCH] Fix documentation typo The correct section for configuring token provider is [token] (singluar) not [tokens]. Change-Id: I52c0290bbba0e8c5e9196a87d8123816b3a2de04 --- keystone/conf/jwt_tokens.py | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/keystone/conf/jwt_tokens.py b/keystone/conf/jwt_tokens.py index d46f815b9c..3b237e4aca 100644 --- a/keystone/conf/jwt_tokens.py +++ b/keystone/conf/jwt_tokens.py @@ -24,7 +24,7 @@ directory must exist in order for keystone's server process to start. It must also be readable by keystone's server process. It must contain at least one public key that corresponds to a private key in `keystone.conf [jwt_tokens] jws_private_key_repository`. This option is only applicable in deployments -issuing JWS tokens and setting `keystone.conf [tokens] provider = jws`. +issuing JWS tokens and setting `keystone.conf [token] provider = jws`. """)) jws_private_key_repository = cfg.StrOpt( 'jws_private_key_repository', @@ -39,7 +39,7 @@ this directory, keystone will use a key named `private.pem` to sign tokens. In the future, keystone may support the ability to sign tokens with multiple private keys. For now, only a key named `private.pem` within this directory is required to issue JWS tokens. This option is only applicable in deployments -issuing JWS tokens and setting `keystone.conf [tokens] provider = jws`. +issuing JWS tokens and setting `keystone.conf [token] provider = jws`. """))