Este conteúdo não está disponível no idioma selecionado.
Chapter 7. keystone
The following chapter contains information about the configuration options in the keystone
service.
7.1. keystone.conf
This section contains options for the /etc/keystone/keystone.conf
file.
7.1.1. DEFAULT
The following table outlines the options available under the [DEFAULT]
group in the /etc/keystone/keystone.conf
file.
.
Configuration option = Default value | Type | Description |
---|---|---|
| string value |
Using this feature is NOT recommended. Instead, use the |
| integer value | The pool size limit for connections expiration policy |
| integer value | The time-to-live in sec of idle connections in the pool |
| string value | The default exchange under which topics are scoped. May be overridden by an exchange name specified in the transport_url option. |
| boolean value | If set to true, the logging level will be set to DEBUG instead of the default INFO level. |
| list value | List of package logging levels in logger=LEVEL pairs. This option is ignored if log_config_append is set. |
| string value |
Default |
| integer value | Size of executor thread pool when executor is threading or eventlet. |
| boolean value | Enables or disables fatal status of deprecations. |
| boolean value | If set to true, then the server will return information in HTTP responses that may allow an unauthenticated or authenticated user to get more information than normal, such as additional details about why authentication failed. This may be useful for debugging but is insecure. |
`instance_format = [instance: %(uuid)s] ` | string value | The format for an instance that is passed with the log message. |
`instance_uuid_format = [instance: %(uuid)s] ` | string value | The format for an instance UUID that is passed with the log message. |
| integer value |
The maximum number of entities that will be returned in a collection. This global limit may be then overridden for a specific driver, by specifying a list_limit in the appropriate section (for example, |
| string value | The name of a logging configuration file. This file is appended to any existing logging configuration files. For details about logging configuration files, see the Python logging module documentation. Note that when logging configuration files are used then all logging configuration is set in the configuration file and other logging configuration options are ignored (for example, log-date-format). |
| string value | Defines the format string for %%(asctime)s in log records. Default: %(default)s . This option is ignored if log_config_append is set. |
| string value | (Optional) The base directory used for relative log_file paths. This option is ignored if log_config_append is set. |
| string value | (Optional) Name of log file to send logging output to. If no default is set, logging will go to stderr as defined by use_stderr. This option is ignored if log_config_append is set. |
| integer value | The amount of time before the log files are rotated. This option is ignored unless log_rotation_type is set to "interval". |
| string value | Rotation interval type. The time of the last file change (or the time when the service was started) is used when scheduling the next rotation. |
| string value | Log rotation type. |
| string value | Format string to use for log messages with context. Used by oslo_log.formatters.ContextFormatter |
| string value | Additional data to append to log message when logging level for the message is DEBUG. Used by oslo_log.formatters.ContextFormatter |
| string value | Format string to use for log messages when context is undefined. Used by oslo_log.formatters.ContextFormatter |
| string value | Prefix each line of exception output with this format. Used by oslo_log.formatters.ContextFormatter |
| string value | Defines the format string for %(user_identity)s that is used in logging_context_format_string. Used by oslo_log.formatters.ContextFormatter |
| integer value | Maximum number of rotated log files. |
| integer value | Log file maximum size in MB. This option is ignored if "log_rotation_type" is not set to "size". |
| integer value | Limit the sizes of user & project ID/names. |
| integer value | Maximum depth of the project hierarchy, excluding the project acting as a domain at the top of the hierarchy. WARNING: Setting it to a large value may adversely impact performance. |
| integer value |
Similar to |
| string value |
Define the notification format for identity service events. A |
| multi valued |
You can reduce the number of notifications keystone emits by explicitly opting out. Keystone will not emit notifications that match the patterns expressed in this list. Values are expected to be in the form of |
| uri value |
The base public endpoint URL for Keystone that is advertised to clients (NOTE: this does NOT affect how Keystone listens for connections). Defaults to the base host URL of the request. For example, if keystone receives a request to |
| boolean value | Enables or disables publication of error events. |
| integer value | Maximum number of logged messages per rate_limit_interval. |
| string value | Log level name used by rate limiting: CRITICAL, ERROR, INFO, WARNING, DEBUG or empty string. Logs with level greater or equal to rate_limit_except_level are not filtered. An empty string means that all levels are filtered. |
| integer value | Interval, number of seconds, of log rate limiting. |
| integer value | Size of RPC connection pool. |
| boolean value | Add an endpoint to answer to ping calls. Endpoint is named oslo_rpc_server_ping |
| integer value | Seconds to wait for a response from a call. |
| boolean value | If set to true, strict password length checking is performed for password manipulation. If a password exceeds the maximum length, the operation will fail with an HTTP 403 Forbidden error. If set to false, passwords are automatically truncated to the maximum length. |
| string value | Syslog facility to receive log lines. This option is ignored if log_config_append is set. |
| string value | The network address and optional user credentials for connecting to the messaging backend, in URL format. The expected format is: driver://[user:pass@]host:port[,[userN:passN@]hostN:portN]/virtual_host?query Example: rabbit://rabbitmq:password@127.0.0.1:5672// For full details on the fields in the URL see the documentation of oslo_messaging.TransportURL at https://docs.openstack.org/oslo.messaging/latest/reference/transport.html |
| boolean value | Enable journald for logging. If running in a systemd environment you may wish to enable journal support. Doing so will use the journal native protocol which includes structured metadata in addition to log messages.This option is ignored if log_config_append is set. |
| boolean value | Use JSON formatting for logging. This option is ignored if log_config_append is set. |
| boolean value | Use syslog for logging. Existing syslog format is DEPRECATED and will be changed later to honor RFC5424. This option is ignored if log_config_append is set. |
| boolean value | Log output to Windows Event Log. |
| boolean value | Log output to standard error. This option is ignored if log_config_append is set. |
| boolean value | Uses logging handler designed to watch file system. When log file is moved or removed this handler will open a new log file with specified path instantaneously. It makes sense only if log_file option is specified and Linux platform is used. This option is ignored if log_config_append is set. |
7.1.2. application_credential
The following table outlines the options available under the [application_credential]
group in the /etc/keystone/keystone.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| integer value | Time to cache application credential data in seconds. This has no effect unless global caching is enabled. |
| boolean value | Toggle for application credential caching. This has no effect unless global caching is enabled. |
| string value |
Entry point for the application credential backend driver in the |
| integer value | Maximum number of application credentials a user is permitted to create. A value of -1 means unlimited. If a limit is not set, users are permitted to create application credentials at will, which could lead to bloat in the keystone database or open keystone to a DoS attack. |
7.1.3. assignment
The following table outlines the options available under the [assignment]
group in the /etc/keystone/keystone.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| string value |
Entry point for the assignment backend driver (where role assignments are stored) in the |
| list value | A list of role names which are prohibited from being an implied role. |
7.1.4. auth
The following table outlines the options available under the [auth]
group in the /etc/keystone/keystone.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| string value |
Entry point for the application_credential auth plugin module in the |
| string value |
Entry point for the external ( |
| string value |
Entry point for the mapped auth plugin module in the |
| list value |
Allowed authentication methods. Note: You should disable the |
| string value |
Entry point for the OAuth 1.0a auth plugin module in the |
| string value |
Entry point for the password auth plugin module in the |
| string value |
Entry point for the token auth plugin module in the |
7.1.5. cache
The following table outlines the options available under the [cache]
group in the /etc/keystone/keystone.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| string value | Cache backend module. For eventlet-based or environments with hundreds of threaded servers, Memcache with pooling (oslo_cache.memcache_pool) is recommended. For environments with less than 100 threaded servers, Memcached (dogpile.cache.memcached) or Redis (dogpile.cache.redis) is recommended. Test environments with a single instance of the server can use the dogpile.cache.memory backend. |
| multi valued | Arguments supplied to the backend module. Specify this option once per argument to be passed to the dogpile.cache backend. Example format: "<argname>:<value>". |
| string value | Prefix for building the configuration dictionary for the cache region. This should not need to be changed unless there is another dogpile.cache region with the same configuration name. |
| floating point value | Time in seconds before attempting to add a node back in the pool in the HashClient’s internal mechanisms. |
| boolean value | Extra debugging from the cache backend (cache keys, get/set/delete/etc calls). This is only really useful if you need to see the specific cache-backend get/set/delete calls with the keys/values. Typically this should be left set to false. |
| boolean value | Enable retry client mechanisms to handle failure. Those mechanisms can be used to wrap all kind of pymemcache clients. The wrapper allows you to define how many attempts to make and how long to wait between attemots. |
| boolean value | Global toggle for the socket keepalive of dogpile’s pymemcache backend |
| boolean value | Global toggle for caching. |
| integer value | Default TTL, in seconds, for any cached item in the dogpile.cache region. This applies to any cached method that doesn’t have an explicit cache expiration time defined for it. |
| integer value | Amount of times a client should be tried before it is marked dead and removed from the pool in the HashClient’s internal mechanisms. |
| floating point value | Time in seconds that should pass between retry attempts in the HashClient’s internal mechanisms. |
| integer value | Number of seconds memcached server is considered dead before it is tried again. (dogpile.cache.memcache and oslo_cache.memcache_pool backends only). |
`memcache_password = ` | string value | the password for the memcached which SASL enabled |
| integer value | Number of seconds that an operation will wait to get a memcache client connection. |
| boolean value | Global toggle if memcache will be flushed on reconnect. (oslo_cache.memcache_pool backend only). |
| integer value | Max total number of open connections to every memcached server. (oslo_cache.memcache_pool backend only). |
| integer value | Number of seconds a connection to memcached is held unused in the pool before it is closed. (oslo_cache.memcache_pool backend only). |
| boolean value | Enable the SASL(Simple Authentication and SecurityLayer) if the SASL_enable is true, else disable. |
| list value |
Memcache servers in the format of "host:port". This is used by backends dependent on Memcached.If |
| floating point value | Timeout in seconds for every call to a server. (dogpile.cache.memcache and oslo_cache.memcache_pool backends only). |
`memcache_username = ` | string value | the user name for the memcached which SASL enabled |
| list value | Proxy classes to import that will affect the way the dogpile.cache backend functions. See the dogpile.cache documentation on changing-backend-behavior. |
| integer value | Number of times to attempt an action before failing. |
| floating point value | Number of seconds to sleep between each attempt. |
| integer value | The maximum number of keepalive probes TCP should send before dropping the connection. Should be a positive integer greater than zero. |
| integer value | The time (in seconds) the connection needs to remain idle before TCP starts sending keepalive probes. Should be a positive integer most greater than zero. |
| integer value | The time (in seconds) between individual keepalive probes. Should be a positive integer greater than zero. |
| string value | Set the available ciphers for sockets created with the TLS context. It should be a string in the OpenSSL cipher list format. If not specified, all OpenSSL enabled ciphers will be available. |
| string value | Path to a file of concatenated CA certificates in PEM format necessary to establish the caching servers' authenticity. If tls_enabled is False, this option is ignored. |
| string value | Path to a single file in PEM format containing the client’s certificate as well as any number of CA certificates needed to establish the certificate’s authenticity. This file is only required when client side authentication is necessary. If tls_enabled is False, this option is ignored. |
| boolean value | Global toggle for TLS usage when comunicating with the caching servers. |
| string value | Path to a single file containing the client’s private key in. Otherwise the private key will be taken from the file specified in tls_certfile. If tls_enabled is False, this option is ignored. |
7.1.6. catalog
The following table outlines the options available under the [catalog]
group in the /etc/keystone/keystone.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| integer value | Time to cache catalog data (in seconds). This has no effect unless global and catalog caching are both enabled. Catalog data (services, endpoints, etc.) typically does not change frequently, and so a longer duration than the global default may be desirable. |
| boolean value | Toggle for catalog caching. This has no effect unless global caching is enabled. In a typical deployment, there is no reason to disable this. |
| string value |
Entry point for the catalog driver in the |
| integer value | Maximum number of entities that will be returned in a catalog collection. There is typically no reason to set this, as it would be unusual for a deployment to have enough services or endpoints to exceed a reasonable limit. |
| string value |
Absolute path to the file used for the templated catalog backend. This option is only used if the |
7.1.7. cors
The following table outlines the options available under the [cors]
group in the /etc/keystone/keystone.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| boolean value | Indicate that the actual request can include user credentials |
| list value | Indicate which header field names may be used during the actual request. |
| list value | Indicate which methods can be used during the actual request. |
| list value | Indicate whether this resource may be shared with the domain received in the requests "origin" header. Format: "<protocol>://<host>[:<port>]", no trailing slash. Example: https://horizon.example.com |
| list value | Indicate which headers are safe to expose to the API. Defaults to HTTP Simple Headers. |
| integer value | Maximum cache age of CORS preflight requests. |
7.1.8. credential
The following table outlines the options available under the [credential]
group in the /etc/keystone/keystone.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| integer value | The length of time in minutes for which a signed EC2 or S3 token request is valid from the timestamp contained in the token request. |
| integer value | Time to cache credential data in seconds. This has no effect unless global caching is enabled. |
| boolean value | Toggle for caching only on retrieval of user credentials. This has no effect unless global caching is enabled. |
| string value |
Entry point for the credential backend driver in the |
| string value | Directory containing Fernet keys used to encrypt and decrypt credentials stored in the credential backend. Fernet keys used to encrypt credentials have no relationship to Fernet keys used to encrypt Fernet tokens. Both sets of keys should be managed separately and require different rotation policies. Do not share this repository with the repository used to manage keys for Fernet tokens. |
| string value |
Entry point for credential encryption and decryption operations in the |
| integer value | Maximum number of credentials a user is permitted to create. A value of -1 means unlimited. If a limit is not set, users are permitted to create credentials at will, which could lead to bloat in the keystone database or open keystone to a DoS attack. |
7.1.9. database
The following table outlines the options available under the [database]
group in the /etc/keystone/keystone.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| string value | The back end to use for the database. |
| string value | The SQLAlchemy connection string to use to connect to the database. |
| integer value | Verbosity of SQL debugging information: 0=None, 100=Everything. |
`connection_parameters = ` | string value | Optional URL parameters to append onto the connection URL at connect time; specify as param1=value1¶m2=value2&… |
| integer value | Connections which have been present in the connection pool longer than this number of seconds will be replaced with a new one the next time they are checked out from the pool. |
| boolean value | Add Python stack traces to SQL as comment strings. |
| boolean value | If True, increases the interval between retries of a database operation up to db_max_retry_interval. |
| integer value | Maximum retries in case of connection error or deadlock error before error is raised. Set to -1 to specify an infinite retry count. |
| integer value | If db_inc_retry_interval is set, the maximum seconds between retries of a database operation. |
| integer value | Seconds between retries of a database transaction. |
| integer value | If set, use this value for max_overflow with SQLAlchemy. |
| integer value | Maximum number of SQL connections to keep open in a pool. Setting a value of 0 indicates no limit. |
| integer value | Maximum number of database connection retries during startup. Set to -1 to specify an infinite retry count. |
| boolean value | If True, transparently enables support for handling MySQL Cluster (NDB). Deprecated since: 12.1.0 *Reason:*Support for the MySQL NDB Cluster storage engine has been deprecated and will be removed in a future release. |
| string value | The SQL mode to be used for MySQL sessions. This option, including the default, overrides any server-set SQL mode. To use whatever SQL mode is set by the server configuration, set this to no value. Example: mysql_sql_mode= |
| integer value | For Galera only, configure wsrep_sync_wait causality checks on new connections. Default is None, meaning don’t configure any setting. |
| integer value | If set, use this value for pool_timeout with SQLAlchemy. |
| integer value | Interval between retries of opening a SQL connection. |
| string value | The SQLAlchemy connection string to use to connect to the slave database. |
| boolean value | If True, SQLite uses synchronous mode. |
| boolean value | Enable the experimental use of database reconnect on connection lost. |
7.1.10. domain_config
The following table outlines the options available under the [domain_config]
group in the /etc/keystone/keystone.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| integer value |
Time-to-live (TTL, in seconds) to cache domain-specific configuration data. This has no effect unless |
| boolean value | Toggle for caching of the domain-specific configuration backend. This has no effect unless global caching is enabled. There is normally no reason to disable this. |
| string value |
Entry point for the domain-specific configuration driver in the |
7.1.11. endpoint_filter
The following table outlines the options available under the [endpoint_filter]
group in the /etc/keystone/keystone.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| string value |
Entry point for the endpoint filter driver in the |
| boolean value | This controls keystone’s behavior if the configured endpoint filters do not result in any endpoints for a user + project pair (and therefore a potentially empty service catalog). If set to true, keystone will return the entire service catalog. If set to false, keystone will return an empty service catalog. |
7.1.12. endpoint_policy
The following table outlines the options available under the [endpoint_policy]
group in the /etc/keystone/keystone.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| string value |
Entry point for the endpoint policy driver in the |
7.1.13. eventlet_server
The following table outlines the options available under the [eventlet_server]
group in the /etc/keystone/keystone.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| host address value | The IP address of the network interface for the admin service to listen on. Deprecated since: K *Reason:*Support for running keystone under eventlet has been removed in the Newton release. These options remain for backwards compatibility because they are used for URL substitutions. |
| port value | The port number for the admin service to listen on. Deprecated since: K *Reason:*Support for running keystone under eventlet has been removed in the Newton release. These options remain for backwards compatibility because they are used for URL substitutions. |
| host address value | The IP address of the network interface for the public service to listen on. Deprecated since: K *Reason:*Support for running keystone under eventlet has been removed in the Newton release. These options remain for backwards compatibility because they are used for URL substitutions. |
| port value | The port number for the public service to listen on. Deprecated since: K *Reason:*Support for running keystone under eventlet has been removed in the Newton release. These options remain for backwards compatibility because they are used for URL substitutions. |
7.1.14. federation
The following table outlines the options available under the [federation]
group in the /etc/keystone/keystone.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
`assertion_prefix = ` | string value | Prefix to use when filtering environment variable names for federated assertions. Matched variables are passed into the federated mapping engine. |
| boolean value | Toggle for federation caching. This has no effect unless global caching is enabled. There is typically no reason to disable this. |
| integer value | Default time in minutes for the validity of group memberships carried over from a mapping. Default is 0, which means disabled. |
| string value |
Entry point for the federation backend driver in the |
| string value | An arbitrary domain name that is reserved to allow federated ephemeral users to have a domain concept. Note that an admin will not be able to create a domain with this name or update an existing domain to this name. You are not advised to change this value unless you really have to. Deprecated since: T *Reason:*This option has been superseded by ephemeral users existing in the domain of their identity provider. |
| string value |
Default value for all protocols to be used to obtain the entity ID of the Identity Provider from the environment. For |
| string value | Absolute path to an HTML file used as a Single Sign-On callback handler. This page is expected to redirect the user from keystone back to a trusted dashboard host, by form encoding a token in a POST request. Keystone’s default value should be sufficient for most deployments. |
| multi valued | A list of trusted dashboard hosts. Before accepting a Single Sign-On request to return a token, the origin host must be a member of this list. This configuration option may be repeated for multiple values. You must set this in order to use web-based SSO flows. For example: trusted_dashboard=https://acme.example.com/auth/websso trusted_dashboard=https://beta.example.com/auth/websso |
7.1.15. fernet_receipts
The following table outlines the options available under the [fernet_receipts]
group in the /etc/keystone/keystone.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| string value |
Directory containing Fernet receipt keys. This directory must exist before using |
| integer value |
This controls how many keys are held in rotation by |
7.1.16. fernet_tokens
The following table outlines the options available under the [fernet_tokens]
group in the /etc/keystone/keystone.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| string value |
Directory containing Fernet token keys. This directory must exist before using |
| integer value |
This controls how many keys are held in rotation by |
7.1.17. healthcheck
The following table outlines the options available under the [healthcheck]
group in the /etc/keystone/keystone.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| list value | Additional backends that can perform health checks and report that information back as part of a request. |
| boolean value | Show more detailed information as part of the response. Security note: Enabling this option may expose sensitive details about the service being monitored. Be sure to verify that it will not violate your security policies. |
| string value | Check the presence of a file to determine if an application is running on a port. Used by DisableByFileHealthcheck plugin. |
| list value | Check the presence of a file based on a port to determine if an application is running on a port. Expects a "port:path" list of strings. Used by DisableByFilesPortsHealthcheck plugin. |
| string value | The path to respond to healtcheck requests on. |
7.1.18. identity
The following table outlines the options available under the [identity]
group in the /etc/keystone/keystone.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| integer value | Time to cache identity data (in seconds). This has no effect unless global and identity caching are enabled. |
| boolean value | Toggle for identity caching. This has no effect unless global caching is enabled. There is typically no reason to disable this. |
| string value |
This references the domain to use for all Identity API v2 requests (which are not aware of domains). A domain with this ID can optionally be created for you by |
| string value |
Absolute path where keystone should locate domain-specific |
| boolean value |
By default, domain-specific configuration data is read from files in the directory identified by |
| boolean value |
A subset (or all) of domains can have their own identity driver, each with their own partial configuration options, stored in either the resource backend or in a file in a domain configuration directory (depending on the setting of |
| string value |
Entry point for the identity backend driver in the |
| integer value | Maximum number of entities that will be returned in an identity collection. |
| integer value | Maximum allowed length for user passwords. Decrease this value to improve performance. Changing this value does not effect existing passwords. This value can also be overridden by certain hashing algorithms maximum allowed length which takes precedence over the configured value. The bcrypt max_password_length is 72 bytes. |
| string value | The password hashing algorithm to use for passwords stored within keystone. |
| integer value |
This option represents a trade off between security and performance. Higher values lead to slower performance, but higher security. Changing this option will only affect newly created passwords as existing password hashes already have a fixed number of rounds applied, so it is safe to tune this option in a running cluster. The default for bcrypt is 12, must be between 4 and 31, inclusive. The default for scrypt is 16, must be within |
| integer value | Number of bytes to use in scrypt and pbkfd2_sha512 hashing salt. Default for scrypt is 16 bytes. Default for pbkfd2_sha512 is 16 bytes. Limited to a maximum of 96 bytes due to the size of the column used to store password hashes. |
| integer value |
Optional block size to pass to scrypt hash function (the |
| integer value |
Optional parallelism to pass to scrypt hash function (the |
7.1.19. identity_mapping
The following table outlines the options available under the [identity_mapping]
group in the /etc/keystone/keystone.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| boolean value |
The format of user and group IDs changed in Juno for backends that do not generate UUIDs (for example, LDAP), with keystone providing a hash mapping to the underlying attribute in LDAP. By default this mapping is disabled, which ensures that existing IDs will not change. Even when the mapping is enabled by using domain-specific drivers ( |
| string value |
Entry point for the identity mapping backend driver in the |
| string value |
Entry point for the public ID generator for user and group entities in the |
7.1.20. jwt_tokens
The following table outlines the options available under the [jwt_tokens]
group in the /etc/keystone/keystone.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| string value |
Directory containing private keys for signing JWS tokens. This 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 private key that corresponds to a public key in |
| string value |
Directory containing public keys for validating JWS token signatures. This 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 |
7.1.21. ldap
The following table outlines the options available under the [ldap]
group in the /etc/keystone/keystone.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| string value |
The LDAP dereferencing option to use for queries involving aliases. A value of |
| integer value |
The maximum end user authentication connection lifetime to the LDAP server in seconds. When this lifetime is exceeded, the connection will be unbound and removed from the connection pool. This option has no effect unless |
| integer value |
The size of the connection pool to use for end user authentication. This option has no effect unless |
| boolean value | Sets keystone’s referral chasing behavior across directory partitions. If left unset, the system’s default behavior will be used. |
| integer value |
The connection timeout to use with the LDAP server. A value of |
| integer value | Sets the LDAP debugging level for LDAP calls. A value of 0 means that debugging is not enabled. This value is a bitmask, consult your LDAP documentation for possible values. |
| boolean value | If enabled, group queries will use Active Directory specific filters for nested groups. |
| list value |
A list of LDAP attribute to keystone group attribute pairs used for mapping additional attributes to groups in keystone. The expected format is |
| list value | List of group attributes to ignore on create and update. or whether a specific group attribute should be filtered for list or show group. |
| string value | The LDAP attribute mapped to group descriptions in keystone. |
| string value | The LDAP search filter to use for groups. |
| string value | The LDAP attribute mapped to group IDs in keystone. This must NOT be a multivalued attribute. Group IDs are expected to be globally unique across keystone domains and URL-safe. |
| string value | The LDAP attribute used to indicate that a user is a member of the group. |
| boolean value |
Enable this option if the members of the group object class are keystone user IDs rather than LDAP DNs. This is the case when using |
| string value | The LDAP attribute mapped to group names in keystone. Group names are expected to be unique only within a keystone domain and are not expected to be URL-safe. |
| string value |
The LDAP object class to use for groups. If setting this option to |
| string value |
The search base to use for groups. Defaults to |
| integer value |
Defines the maximum number of results per page that keystone should request from the LDAP server when listing objects. A value of zero ( |
| string value | The password of the administrator bind DN to use when querying the LDAP server, if your LDAP server requires it. |
| integer value |
The maximum connection lifetime to the LDAP server in seconds. When this lifetime is exceeded, the connection will be unbound and removed from the connection pool. This option has no effect unless |
| integer value |
The connection timeout to use when pooling LDAP connections. A value of |
| floating point value |
The number of seconds to wait before attempting to reconnect to the LDAP server. This option has no effect unless |
| integer value |
The maximum number of times to attempt connecting to the LDAP server before aborting. A value of one makes only one connection attempt. This option has no effect unless |
| integer value |
The size of the LDAP connection pool. This option has no effect unless |
| string value |
The search scope which defines how deep to search within the search base. A value of |
| boolean value | Randomize the order of URLs in each keystone process. This makes the failure behavior more gradual, since if the first server is down, a process/thread will wait for the specified timeout before attempting a connection to a server further down the list. This defaults to False, for backward compatibility. |
| string value |
The default LDAP server suffix to use, if a DN is not defined via either |
| string value |
An absolute path to a CA certificate directory to use when communicating with LDAP servers. There is no reason to set this option if you’ve also set |
| string value |
An absolute path to a CA certificate file to use when communicating with LDAP servers. This option will take precedence over |
| string value |
Specifies which checks to perform against client certificates on incoming TLS sessions. If set to |
| string value | URL(s) for connecting to the LDAP server. Multiple LDAP URLs may be specified as a comma separated string. The first URL to successfully bind is used for the connection. |
| boolean value | Enable LDAP connection pooling for end user authentication. There is typically no reason to disable this. |
| boolean value | Enable LDAP connection pooling for queries to the LDAP server. There is typically no reason to disable this. |
| boolean value |
Enable TLS when communicating with LDAP servers. You should also set the |
| string value | The user name of the administrator bind DN to use when querying the LDAP server, if your LDAP server requires it. |
| list value |
A list of LDAP attribute to keystone user attribute pairs used for mapping additional attributes to users in keystone. The expected format is |
| list value | List of user attributes to ignore on create and update, or whether a specific user attribute should be filtered for list or show user. |
| string value | The LDAP attribute mapped to a user’s default_project_id in keystone. This is most commonly used when keystone has write access to LDAP. |
| string value | The LDAP attribute mapped to user descriptions in keystone. |
| string value |
The LDAP attribute mapped to the user enabled attribute in keystone. If setting this option to |
| string value |
The default value to enable users. This should match an appropriate integer value if the LDAP server uses non-boolean (bitmask) values to indicate if a user is enabled or disabled. If this is not set to |
| boolean value |
If enabled, keystone uses an alternative method to determine if a user is enabled or not by checking if they are a member of the group defined by the |
| string value |
DN of the group entry to hold enabled users when using enabled emulation. Setting this option has no effect unless |
| boolean value |
Use the |
| boolean value |
Logically negate the boolean value of the enabled attribute obtained from the LDAP server. Some LDAP servers use a boolean lock attribute where "true" means an account is disabled. Setting |
| integer value |
Bitmask integer to select which bit indicates the enabled value if the LDAP server represents "enabled" as a bit on an integer rather than as a discrete boolean. A value of |
| string value | The LDAP search filter to use for users. |
| string value | The LDAP attribute mapped to user IDs in keystone. This must NOT be a multivalued attribute. User IDs are expected to be globally unique across keystone domains and URL-safe. |
| string value | The LDAP attribute mapped to user emails in keystone. |
| string value | The LDAP attribute mapped to user names in keystone. User names are expected to be unique only within a keystone domain and are not expected to be URL-safe. |
| string value | The LDAP object class to use for users. |
| string value | The LDAP attribute mapped to user passwords in keystone. |
| string value |
The search base to use for users. Defaults to |
7.1.22. memcache
The following table outlines the options available under the [memcache]
group in the /etc/keystone/keystone.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| integer value | Number of seconds memcached server is considered dead before it is tried again. This is used by the key value store system. Deprecated since: Y *Reason:*This option has no effect. Configure ``keystone.conf [cache] memcache_dead_retry`` option to set the dead_retry of memcached instead. |
| integer value | Number of seconds that an operation will wait to get a memcache client connection. This is used by the key value store system. Deprecated since: Y *Reason:*This option has no effect. Configure ``keystone.conf [cache] memcache_pool_connection_get_timeout`` option to set the connection_get_timeout of memcached instead. |
| integer value | Max total number of open connections to every memcached server. This is used by the key value store system. Deprecated since: Y *Reason:*This option has no effect. Configure ``keystone.conf [cache] memcache_pool_maxsize`` option to set the pool_maxsize of memcached instead. |
| integer value | Number of seconds a connection to memcached is held unused in the pool before it is closed. This is used by the key value store system. Deprecated since: Y *Reason:*This option has no effect. Configure ``keystone.conf [cache] memcache_pool_unused_timeout`` option to set the pool_unused_timeout of memcached instead. |
| integer value | Timeout in seconds for every call to a server. This is used by the key value store system. Deprecated since: T *Reason:*This option has no effect. Configure ``keystone.conf [cache] memcache_socket_timeout`` option to set the socket_timeout of memcached instead. |
7.1.23. oauth1
The following table outlines the options available under the [oauth1]
group in the /etc/keystone/keystone.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| integer value | Number of seconds for the OAuth Access Token to remain valid after being created. This is the amount of time the consumer has to interact with the service provider (which is typically keystone). Setting this option to zero means that access tokens will last forever. |
| string value |
Entry point for the OAuth backend driver in the |
| integer value | Number of seconds for the OAuth Request Token to remain valid after being created. This is the amount of time the user has to authorize the token. Setting this option to zero means that request tokens will last forever. |
7.1.24. oauth2
The following table outlines the options available under the [oauth2]
group in the /etc/keystone/keystone.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| list value | The OAuth2.0 authentication method supported by the system when user obtains an access token through the OAuth2.0 token endpoint. This option can be set to certificate or secret. If the option is not set, the default value is certificate. When the option is set to secret, the OAuth2.0 token endpoint uses client_secret_basic method for authentication, otherwise tls_client_auth method is used for authentication. |
| string value | Used to define the mapping rule id. When not set, the mapping rule id is oauth2_mapping. |
7.1.25. oslo_messaging_amqp
The following table outlines the options available under the [oslo_messaging_amqp]
group in the /etc/keystone/keystone.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| string value | Indicates the addressing mode used by the driver. Permitted values: legacy - use legacy non-routable addressing routable - use routable addresses dynamic - use legacy addresses if the message bus does not support routing otherwise use routable addressing |
| string value | Appended to the address prefix when sending to a group of consumers. Used by the message bus to identify messages that should be delivered in a round-robin fashion across consumers. |
| string value | address prefix used when broadcasting to all servers |
| integer value | Increase the connection_retry_interval by this many seconds after each unsuccessful failover attempt. |
| integer value | Seconds to pause before attempting to re-connect. |
| integer value | Maximum limit for connection_retry_interval + connection_retry_backoff |
| string value | Name for the AMQP container. must be globally unique. Defaults to a generated UUID |
| string value | Exchange name used in notification addresses. Exchange name resolution precedence: Target.exchange if set else default_notification_exchange if set else control_exchange if set else notify |
| integer value | The deadline for a sent notification message delivery. Only used when caller does not provide a timeout expiry. |
| integer value | The maximum number of attempts to re-send a reply message which failed due to a recoverable error. |
| integer value | The deadline for an rpc reply message delivery. |
| string value | Exchange name used in RPC addresses. Exchange name resolution precedence: Target.exchange if set else default_rpc_exchange if set else control_exchange if set else rpc |
| integer value | The deadline for an rpc cast or call message delivery. Only used when caller does not provide a timeout expiry. |
| integer value | The duration to schedule a purge of idle sender links. Detach link after expiry. |
| string value | address prefix when sending to any server in group |
| integer value | Timeout for inactive connections (in seconds) |
| integer value | Time to pause between re-connecting an AMQP 1.0 link that failed due to a recoverable error. |
| string value | Appended to the address prefix when sending a fanout message. Used by the message bus to identify fanout messages. |
| string value | Address prefix for all generated Notification addresses |
| integer value | Window size for incoming Notification messages |
| multi valued | Send messages of this type pre-settled. Pre-settled messages will not receive acknowledgement from the peer. Note well: pre-settled messages may be silently discarded if the delivery fails. Permitted values: rpc-call - send RPC Calls pre-settled rpc-reply- send RPC Replies pre-settled rpc-cast - Send RPC Casts pre-settled notify - Send Notifications pre-settled |
| boolean value | Enable virtual host support for those message buses that do not natively support virtual hosting (such as qpidd). When set to true the virtual host name will be added to all message bus addresses, effectively creating a private subnet per virtual host. Set to False if the message bus supports virtual hosting using the hostname field in the AMQP 1.0 Open performative as the name of the virtual host. |
| integer value | Window size for incoming RPC Reply messages. |
| string value | Address prefix for all generated RPC addresses |
| integer value | Window size for incoming RPC Request messages |
`sasl_config_dir = ` | string value | Path to directory that contains the SASL configuration |
`sasl_config_name = ` | string value | Name of configuration file (without .conf suffix) |
`sasl_default_realm = ` | string value | SASL realm to use if no realm present in username |
`sasl_mechanisms = ` | string value | Space separated list of acceptable SASL mechanisms |
| string value | address prefix used when sending to a specific server |
| boolean value | Attempt to connect via SSL. If no other ssl-related parameters are given, it will use the system’s CA-bundle to verify the server’s certificate. |
`ssl_ca_file = ` | string value | CA certificate PEM file used to verify the server’s certificate |
`ssl_cert_file = ` | string value | Self-identifying certificate PEM file for client authentication |
`ssl_key_file = ` | string value | Private key PEM file used to sign ssl_cert_file certificate (optional) |
| string value | Password for decrypting ssl_key_file (if encrypted) |
| boolean value | By default SSL checks that the name in the server’s certificate matches the hostname in the transport_url. In some configurations it may be preferable to use the virtual hostname instead, for example if the server uses the Server Name Indication TLS extension (rfc6066) to provide a certificate per virtual host. Set ssl_verify_vhost to True if the server’s SSL certificate uses the virtual host name instead of the DNS name. |
| boolean value | Debug: dump AMQP frames to stdout |
| string value | Appended to the address prefix when sending to a particular RPC/Notification server. Used by the message bus to identify messages sent to a single destination. |
7.1.26. oslo_messaging_kafka
The following table outlines the options available under the [oslo_messaging_kafka]
group in the /etc/keystone/keystone.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| string value | The compression codec for all data generated by the producer. If not set, compression will not be used. Note that the allowed values of this depend on the kafka version |
| integer value | The pool size limit for connections expiration policy |
| integer value | The time-to-live in sec of idle connections in the pool |
| string value | Group id for Kafka consumer. Consumers in one group will coordinate message consumption |
| boolean value | Enable asynchronous consumer commits |
| floating point value | Default timeout(s) for Kafka consumers |
| integer value | Max fetch bytes of Kafka consumer |
| integer value | The maximum number of records returned in a poll call |
| integer value | Pool Size for Kafka Consumers |
| integer value | Size of batch for the producer async send |
| floating point value | Upper bound on the delay for KafkaProducer batching in seconds |
| string value | Mechanism when security protocol is SASL |
| string value | Protocol used to communicate with brokers |
`ssl_cafile = ` | string value | CA certificate PEM file used to verify the server certificate |
`ssl_client_cert_file = ` | string value | Client certificate PEM file used for authentication. |
`ssl_client_key_file = ` | string value | Client key PEM file used for authentication. |
`ssl_client_key_password = ` | string value | Client key password file used for authentication. |
7.1.27. oslo_messaging_notifications
The following table outlines the options available under the [oslo_messaging_notifications]
group in the /etc/keystone/keystone.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| multi valued | The Drivers(s) to handle sending notifications. Possible values are messaging, messagingv2, routing, log, test, noop |
| integer value | The maximum number of attempts to re-send a notification message which failed to be delivered due to a recoverable error. 0 - No retry, -1 - indefinite |
| list value | AMQP topic used for OpenStack notifications. |
| string value | A URL representing the messaging driver to use for notifications. If not set, we fall back to the same configuration used for RPC. |
7.1.28. oslo_messaging_rabbit
The following table outlines the options available under the [oslo_messaging_rabbit]
group in the /etc/keystone/keystone.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| boolean value | Auto-delete queues in AMQP. |
| boolean value | Use durable queues in AMQP. If rabbit_quorum_queue is enabled, queues will be durable and this value will be ignored. |
| boolean value | (DEPRECATED) Enable/Disable the RabbitMQ mandatory flag for direct send. The direct send is used as reply, so the MessageUndeliverable exception is raised in case the client queue does not exist.MessageUndeliverable exception will be used to loop for a timeout to lets a chance to sender to recover.This flag is deprecated and it will not be possible to deactivate this functionality anymore |
| boolean value | Enable x-cancel-on-ha-failover flag so that rabbitmq server will cancel and notify consumerswhen queue is down |
| boolean value | Run the health check heartbeat thread through a native python thread by default. If this option is equal to False then the health check heartbeat will inherit the execution model from the parent process. For example if the parent process has monkey patched the stdlib by using eventlet/greenlet then the heartbeat will be run through a green thread. This option should be set to True only for the wsgi services. |
| integer value | How often times during the heartbeat_timeout_threshold we check the heartbeat. |
| integer value | Number of seconds after which the Rabbit broker is considered down if heartbeat’s keep-alive fails (0 disables heartbeat). |
| string value | EXPERIMENTAL: Possible values are: gzip, bz2. If not set compression will not be used. This option may not be available in future versions. |
| string value | Determines how the next RabbitMQ node is chosen in case the one we are currently connected to becomes unavailable. Takes effect only if more than one RabbitMQ node is provided in config. |
| integer value | How long to wait a missing client before abandoning to send it its replies. This value should not be longer than rpc_response_timeout. |
| floating point value | How long to wait (in seconds) before reconnecting in response to an AMQP consumer cancel notification. |
| boolean value | Try to use HA queues in RabbitMQ (x-ha-policy: all). If you change this option, you must wipe the RabbitMQ database. In RabbitMQ 3.0, queue mirroring is no longer controlled by the x-ha-policy argument when declaring a queue. If you just want to make sure that all queues (except those with auto-generated names) are mirrored across all nodes, run: "rabbitmqctl set_policy HA ^(?!amq\.).* {"ha-mode": "all"} " |
| integer value | Maximum interval of RabbitMQ connection retries. Default is 30 seconds. |
| string value | The RabbitMQ login method. |
| integer value | Specifies the number of messages to prefetch. Setting to zero allows unlimited messages. |
| integer value | Each time a message is redelivered to a consumer, a counter is incremented. Once the redelivery count exceeds the delivery limit the message gets dropped or dead-lettered (if a DLX exchange has been configured) Used only when rabbit_quorum_queue is enabled, Default 0 which means dont set a limit. |
| integer value | By default all messages are maintained in memory if a quorum queue grows in length it can put memory pressure on a cluster. This option can limit the number of memory bytes used by the quorum queue. Used only when rabbit_quorum_queue is enabled, Default 0 which means dont set a limit. |
| integer value | By default all messages are maintained in memory if a quorum queue grows in length it can put memory pressure on a cluster. This option can limit the number of messages in the quorum queue. Used only when rabbit_quorum_queue is enabled, Default 0 which means dont set a limit. |
| boolean value |
Use quorum queues in RabbitMQ (x-queue-type: quorum). The quorum queue is a modern queue type for RabbitMQ implementing a durable, replicated FIFO queue based on the Raft consensus algorithm. It is available as of RabbitMQ 3.8.0. If set this option will conflict with the HA queues ( |
| integer value | How long to backoff for between retries when connecting to RabbitMQ. |
| integer value | How frequently to retry connecting with RabbitMQ. |
| integer value | Positive integer representing duration in seconds for queue TTL (x-expires). Queues which are unused for the duration of the TTL are automatically deleted. The parameter affects only reply and fanout queues. |
| boolean value | Connect over SSL. |
`ssl_ca_file = ` | string value | SSL certification authority file (valid only if SSL enabled). |
`ssl_cert_file = ` | string value | SSL cert file (valid only if SSL enabled). |
| boolean value | Global toggle for enforcing the OpenSSL FIPS mode. This feature requires Python support. This is available in Python 3.9 in all environments and may have been backported to older Python versions on select environments. If the Python executable used does not support OpenSSL FIPS mode, an exception will be raised. |
`ssl_key_file = ` | string value | SSL key file (valid only if SSL enabled). |
`ssl_version = ` | string value | SSL version to use (valid only if SSL enabled). Valid values are TLSv1 and SSLv23. SSLv2, SSLv3, TLSv1_1, and TLSv1_2 may be available on some distributions. |
7.1.29. oslo_middleware
The following table outlines the options available under the [oslo_middleware]
group in the /etc/keystone/keystone.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| boolean value | Whether the application is behind a proxy or not. This determines if the middleware should parse the headers or not. |
| string value | HTTP basic auth password file. |
| integer value | The maximum body size for each request, in bytes. |
| string value | The HTTP Header that will be used to determine what the original request protocol scheme was, even if it was hidden by a SSL termination proxy. |
7.1.30. oslo_policy
The following table outlines the options available under the [oslo_policy]
group in the /etc/keystone/keystone.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| boolean value |
This option controls whether or not to use old deprecated defaults when evaluating policies. If |
| boolean value |
This option controls whether or not to enforce scope when evaluating policies. If |
| string value | Default rule. Enforced when a requested rule is not found. |
| multi valued | Directories where policy configuration files are stored. They can be relative to any directory in the search path defined by the config_dir option, or absolute paths. The file defined by policy_file must exist for these directories to be searched. Missing or empty directories are ignored. |
| string value | The relative or absolute path of a file that maps roles to permissions for a given service. Relative paths must be specified in relation to the configuration file setting this option. |
| string value | Content Type to send and receive data for REST based policy check |
| string value | Absolute path to ca cert file for REST based policy check |
| string value | Absolute path to client cert for REST based policy check |
| string value | Absolute path client key file REST based policy check |
| boolean value | server identity verification for REST based policy check |
7.1.31. policy
The following table outlines the options available under the [policy]
group in the /etc/keystone/keystone.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| string value |
Entry point for the policy backend driver in the |
| integer value | Maximum number of entities that will be returned in a policy collection. |
7.1.32. profiler
The following table outlines the options available under the [profiler]
group in the /etc/keystone/keystone.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| string value | Connection string for a notifier backend.
Default value is Examples of possible values:
|
| boolean value | Enable the profiling for all services on this node. Default value is False (fully disable the profiling feature). Possible values:
|
| string value | Document type for notification indexing in elasticsearch. |
| integer value | Elasticsearch splits large requests in batches. This parameter defines maximum size of each batch (for example: es_scroll_size=10000). |
| string value | This parameter is a time value parameter (for example: es_scroll_time=2m), indicating for how long the nodes that participate in the search will maintain relevant resources in order to continue and support it. |
| boolean value | Enable filter traces that contain error/exception to a separated place. Default value is set to False. Possible values:
|
| string value | Secret key(s) to use for encrypting context data for performance profiling. This string value should have the following format: <key1>[,<key2>,…<keyn>], where each key is some random string. A user who triggers the profiling via the REST API has to set one of these keys in the headers of the REST API call to include profiling results of this node for this particular project. Both "enabled" flag and "hmac_keys" config options should be set to enable profiling. Also, to generate correct profiling information across all services at least one key needs to be consistent between OpenStack projects. This ensures it can be used from client side to generate the trace, containing information from all possible resources. |
| string value |
Redissentinel uses a service name to identify a master redis service. This parameter defines the name (for example: |
| floating point value | Redissentinel provides a timeout option on the connections. This parameter defines that timeout (for example: socket_timeout=0.1). |
| boolean value | Enable SQL requests profiling in services. Default value is False (SQL requests won’t be traced). Possible values:
|
7.1.33. receipt
The following table outlines the options available under the [receipt]
group in the /etc/keystone/keystone.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| boolean value | Enable storing issued receipt data to receipt validation cache so that first receipt validation doesn’t actually cause full validation cycle. This option has no effect unless global caching and receipt caching are enabled. |
| integer value |
The number of seconds to cache receipt creation and validation data. This has no effect unless both global and |
| boolean value | Toggle for caching receipt creation and validation data. This has no effect unless global caching is enabled, or if cache_on_issue is disabled as we only cache receipts on issue. |
| integer value | The amount of time that a receipt should remain valid (in seconds). This value should always be very short, as it represents how long a user has to reattempt auth with the missing auth methods. |
| string value |
Entry point for the receipt provider in the |
7.1.34. resource
The following table outlines the options available under the [resource]
group in the /etc/keystone/keystone.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| string value |
Name of the domain that owns the |
| string value |
This is a special project which represents cloud-level administrator privileges across services. Tokens scoped to this project will contain a true |
| integer value | Time to cache resource data in seconds. This has no effect unless global caching is enabled. |
| boolean value | Toggle for resource caching. This has no effect unless global caching is enabled. |
| string value |
This controls whether the names of domains are restricted from containing URL-reserved characters. If set to |
| string value |
Entry point for the resource driver in the |
| integer value | Maximum number of entities that will be returned in a resource collection. |
| string value |
This controls whether the names of projects are restricted from containing URL-reserved characters. If set to |
7.1.35. revoke
The following table outlines the options available under the [revoke]
group in the /etc/keystone/keystone.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| integer value |
Time to cache the revocation list and the revocation events (in seconds). This has no effect unless global and |
| boolean value | Toggle for revocation event caching. This has no effect unless global caching is enabled. |
| string value |
Entry point for the token revocation backend driver in the |
| integer value | The number of seconds after a token has expired before a corresponding revocation event may be purged from the backend. |
7.1.36. role
The following table outlines the options available under the [role]
group in the /etc/keystone/keystone.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| integer value |
Time to cache role data, in seconds. This has no effect unless both global caching and |
| boolean value | Toggle for role caching. This has no effect unless global caching is enabled. In a typical deployment, there is no reason to disable this. |
| string value |
Entry point for the role backend driver in the |
| integer value | Maximum number of entities that will be returned in a role collection. This may be useful to tune if you have a large number of discrete roles in your deployment. |
7.1.37. saml
The following table outlines the options available under the [saml]
group in the /etc/keystone/keystone.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| integer value |
Determines the lifetime for any SAML assertions generated by keystone, using |
| string value |
Absolute path to the public certificate file to use for SAML signing. The value cannot contain a comma ( |
| string value | This is the company name of the identity provider’s contact person. |
| string value | This is the email address of the identity provider’s contact person. |
| string value | This is the given name of the identity provider’s contact person. |
| string value | This is the surname of the identity provider’s contact person. |
| string value | This is the telephone number of the identity provider’s contact person. |
| string value | This is the type of contact that best describes the identity provider’s contact person. |
| uri value |
This is the unique entity identifier of the identity provider (keystone) to use when generating SAML assertions. This value is required to generate identity provider metadata and must be a URI (a URL is recommended). For example: |
| string value | This is the language used by the identity provider’s organization. |
| string value |
Absolute path to the identity provider metadata file. This file should be generated with the |
| string value | This is the name of the identity provider’s organization to be displayed. |
| string value | This is the name of the identity provider’s organization. |
| uri value | This is the URL of the identity provider’s organization. The URL referenced here should be useful to humans. |
| uri value |
This is the single sign-on (SSO) service location of the identity provider which accepts HTTP POST requests. A value is required to generate identity provider metadata. For example: |
| string value |
Absolute path to the private key file to use for SAML signing. The value cannot contain a comma ( |
| string value | The prefix of the RelayState SAML attribute to use when generating enhanced client and proxy (ECP) assertions. In a typical deployment, there is no reason to change this value. |
| string value |
Name of, or absolute path to, the binary to be used for XML signing. Although only the XML Security Library ( |
7.1.38. security_compliance
The following table outlines the options available under the [security_compliance]
group in the /etc/keystone/keystone.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| boolean value |
Enabling this option requires users to change their password when the user is created, or upon administrative reset. Before accessing any services, affected users will have to change their password. To ignore this requirement for specific users, such as service users, set the |
| integer value |
The maximum number of days a user can go without authenticating before being considered "inactive" and automatically disabled (locked). This feature is disabled by default; set any value to enable it. This feature depends on the |
| integer value |
The number of seconds a user account will be locked when the maximum number of failed authentication attempts (as specified by |
| integer value |
The maximum number of times that a user can fail to authenticate before the user account is locked for the number of seconds specified by |
| integer value |
The number of days that a password must be used before the user can change it. This prevents users from changing their passwords immediately in order to wipe out their password history and reuse an old password. This feature does not prevent administrators from manually resetting passwords. It is disabled by default and allows for immediate password changes. This feature depends on the |
| integer value |
The number of days for which a password will be considered valid before requiring it to be changed. This feature is disabled by default. If enabled, new password changes will have an expiration date, however existing passwords would not be impacted. This feature depends on the |
| string value |
The regular expression used to validate password strength requirements. By default, the regular expression will match any password. The following is an example of a pattern which requires at least 1 letter, 1 digit, and have a minimum length of 7 characters: ^(?=.\\d)(?=.[a-zA-Z]).{7,}$ This feature depends on the |
| string value | Describe your password regular expression here in language for humans. If a password fails to match the regular expression, the contents of this configuration variable will be returned to users to explain why their requested password was insufficient. |
| integer value |
This controls the number of previous user password iterations to keep in history, in order to enforce that newly created passwords are unique. The total number which includes the new password should not be greater or equal to this value. Setting the value to zero (the default) disables this feature. Thus, to enable this feature, values must be greater than 0. This feature depends on the |
7.1.39. shadow_users
The following table outlines the options available under the [shadow_users]
group in the /etc/keystone/keystone.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| string value |
Entry point for the shadow users backend driver in the |
7.1.40. token
The following table outlines the options available under the [token]
group in the /etc/keystone/keystone.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| integer value | This controls the number of seconds that a token can be retrieved for beyond the built-in expiry time. This allows long running operations to succeed. Defaults to two days. |
| boolean value | This toggles whether scoped tokens may be re-scoped to a new project or domain, thereby preventing users from exchanging a scoped token (including those with a default project scope) for any other token. This forces users to either authenticate for unscoped tokens (and later exchange that unscoped token for tokens with a more specific scope) or to provide their credentials in every request for a scoped token to avoid re-scoping altogether. |
| boolean value |
Enable storing issued token data to token validation cache so that first token validation doesn’t actually cause full validation cycle. This option has no effect unless global caching is enabled and will still cache tokens even if *Reason:*Keystone already exposes a configuration option for caching tokens. Having a separate configuration option to cache tokens when they are issued is redundant, unnecessarily complicated, and is misleading if token caching is disabled because tokens will still be pre-cached by default when they are issued. The ability to pre-cache tokens when they are issued is going to rely exclusively on the ``keystone.conf [token] caching`` option in the future. |
| integer value |
The number of seconds to cache token creation and validation data. This has no effect unless both global and |
| boolean value | Toggle for caching token creation and validation data. This has no effect unless global caching is enabled. |
| integer value | The amount of time that a token should remain valid (in seconds). Drastically reducing this value may break "long-running" operations that involve multiple services to coordinate together, and will force users to authenticate with keystone more frequently. Drastically increasing this value will increase the number of tokens that will be simultaneously valid. Keystone tokens are also bearer tokens, so a shorter duration will also reduce the potential security impact of a compromised token. |
| string value |
Entry point for the token provider in the |
| boolean value |
This toggles support for revoking individual tokens by the token identifier and thus various token enumeration operations (such as listing all tokens issued to a specific user). These operations are used to determine the list of tokens to consider revoked. Do not disable this option if you’re using the |
7.1.41. tokenless_auth
The following table outlines the options available under the [tokenless_auth]
group in the /etc/keystone/keystone.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| string value | The name of the WSGI environment variable used to pass the issuer of the client certificate to keystone. This attribute is used as an identity provider ID for the X.509 tokenless authorization along with the protocol to look up its corresponding mapping. In a typical deployment, there is no reason to change this value. |
| string value |
The federated protocol ID used to represent X.509 tokenless authorization. This is used in combination with the value of |
| multi valued |
The list of distinguished names which identify trusted issuers of client certificates allowed to use X.509 tokenless authorization. If the option is absent then no certificates will be allowed. The format for the values of a distinguished name (DN) must be separated by a comma and contain no spaces. Furthermore, because an individual DN may contain commas, this configuration option may be repeated multiple times to represent multiple values. For example, keystone.conf would include two consecutive lines in order to trust two different DNs, such as |
7.1.42. totp
The following table outlines the options available under the [totp]
group in the /etc/keystone/keystone.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| integer value | The number of previous windows to check when processing TOTP passcodes. |
7.1.43. trust
The following table outlines the options available under the [trust]
group in the /etc/keystone/keystone.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| boolean value |
Allows authorization to be redelegated from one user to another, effectively chaining trusts together. When disabled, the |
| string value |
Entry point for the trust backend driver in the |
| integer value | Maximum number of times that authorization can be redelegated from one user to another in a chain of trusts. This number may be reduced further for a specific trust. |
7.1.44. unified_limit
The following table outlines the options available under the [unified_limit]
group in the /etc/keystone/keystone.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| integer value |
Time to cache unified limit data, in seconds. This has no effect unless both global caching and |
| boolean value | Toggle for unified limit caching. This has no effect unless global caching is enabled. In a typical deployment, there is no reason to disable this. |
| string value |
Entry point for the unified limit backend driver in the |
| string value | The enforcement model to use when validating limits associated to projects. Enforcement models will behave differently depending on the existing limits, which may result in backwards incompatible changes if a model is switched in a running deployment. |
| integer value | Maximum number of entities that will be returned in a unified limit collection. This may be useful to tune if you have a large number of unified limits in your deployment. |
7.1.45. wsgi
The following table outlines the options available under the [wsgi]
group in the /etc/keystone/keystone.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| boolean value | If set to true, this enables the oslo debug middleware in Keystone. This Middleware prints a lot of information about the request and the response. It is useful for getting information about the data on the wire (decoded) and passed to the WSGI application pipeline. This middleware has no effect on the "debug" setting in the [DEFAULT] section of the config file or setting Keystone’s log-level to "DEBUG"; it is specific to debugging the WSGI data as it enters and leaves Keystone (specific request-related data). This option is used for introspection on the request and response data between the web server (apache, nginx, etc) and Keystone. This middleware is inserted as the first element in the middleware chain and will show the data closest to the wire. WARNING: NOT INTENDED FOR USE IN PRODUCTION. THIS MIDDLEWARE CAN AND WILL EMIT SENSITIVE/PRIVILEGED DATA. |