Chapter 10. Identity (keystone) Parameters

AdminEmail

The email for the OpenStack Identity (keystone) admin account. The default value is: admin@example.com

AdminPassword

The password for the OpenStack Identity (keystone) admin account.

AdminToken

The OpenStack Identity (keystone) secret and database password.

KeystoneCredential0

The first OpenStack Identity (keystone) credential key. Must be a valid key.

KeystoneCredential1

The second OpenStack Identity (keystone) credential key. Must be a valid key.

KeystoneCronTokenFlushDestination

Cron to purge expired tokens - Log destination. The default value is: /var/log/keystone/keystone-tokenflush.log

KeystoneCronTokenFlushEnsure

Cron to purge expired tokens - Ensure. The default value is: present

KeystoneCronTokenFlushHour

Cron to purge expired tokens - Hour. The default value is: *

KeystoneCronTokenFlushMaxDelay

Cron to purge expired tokens - Max Delay. The default value is: 0

KeystoneCronTokenFlushMinute

Cron to purge expired tokens - Minute. The default value is: 1

KeystoneCronTokenFlushMonth

Cron to purge expired tokens - Month. The default value is: *

KeystoneCronTokenFlushMonthday

Cron to purge expired tokens - Month Day. The default value is: *

KeystoneCronTokenFlushUser

Cron to purge expired tokens - User. The default value is: keystone

KeystoneCronTokenFlushWeekday

Cron to purge expired tokens - Week Day. The default value is: *

KeystoneEnableDBPurge

Whether to create cron job for purging soft deleted rows in OpenStack Identity (keystone) database. The default value is: True

KeystoneNotificationDriver

Comma-separated list of Oslo notification drivers used by Keystone. The default value is: ['messaging']

KeystoneNotificationFormat

The OpenStack Identity (keystone) notification format. The default value is: basic

KeystoneSSLCertificate

Keystone certificate for verifying token validity.

KeystoneSSLCertificateKey

Keystone key for signing tokens.

KeystoneWorkers

Set the number of workers for the OpenStack Identity (keystone) service. The default value is equal to the number of CPU cores on the node. Note that more workers creates a larger number of processes on systems, which results in excess memory consumption. It is recommended to choose a suitable non-default value on systems with high CPU core counts.