Update the ldap configuration guide to use correct defaults
This change goes hand-in-hand with another patch to puppet-keystone [0] that removes default values from puppet-keystone. If configuration values aren't defined in keystone's configuration file, it will use it's defaults. Having defaults in two places just makes it easier for them to get out-of-sync, which is the case in 713708. This updates the docs to reflect the default values in keystone. [0] https://review.opendev.org/#/c/713708/ Change-Id: I95c414be4881a230466527e399f2490659a6b61e
This commit is contained in:
parent
e910f4696e
commit
d2a0f148c4
@ -139,7 +139,7 @@ keys:
|
||||
* **tls_req_cert**: Valid options for tls_req_cert are demand, never, and allow.
|
||||
|
||||
* **use_pool**: Enable LDAP connection pooling. (boolean value and defaults to
|
||||
false)
|
||||
true)
|
||||
|
||||
* **pool_size**: Connection pool size. (integer value and defaults to '10')
|
||||
|
||||
@ -157,7 +157,7 @@ keys:
|
||||
|
||||
* **use_auth_pool**: Enable LDAP connection pooling for end user authentication.
|
||||
If use_pool is disabled, then this setting is meaningless and is not used at
|
||||
all. (boolean value and defaults to false)
|
||||
all. (boolean value and defaults to true)
|
||||
|
||||
* **auth_pool_size**: End user auth connection pool size. (integer value and
|
||||
defaults to '100')
|
||||
|
Loading…
Reference in New Issue
Block a user