keystone.conf [caching] enabled is not enabled.
Caching greatly improves the performance of keystone, and it is highly recommended that you enable it.
Caching is not completely configured.
Although caching is enabled in keystone.conf [cache] enabled, the default backend is still set to the no-op backend. Instead, configure keystone to point to a real caching backend like memcached.
Credential key repository is empty.
After configuring keystone to use the Fernet credential provider, you should use keystone-manage credential_setup to initially populate your key repository with keys, and periodically rotate your keys with keystone-manage credential_rotate.
Key repositories for encryption should be unique.
Even though credentials are encrypted using the same mechanism as Fernet tokens, they should have key repository locations that are independent of one another. Using the same repository to encrypt credentials and tokens can be considered a security vulnerability because ciphertext from the keys used to encrypt credentials is exposed as the token ID. Sharing a key repository can also lead to premature key removal during key rotation. This could result in indecipherable credentials, rendering them completely useless, or early token invalidation because the key that was used to encrypt the entity has been deleted.
Ensure keystone.conf [credential] key_repository and keystone.conf [fernet_tokens] key_repository are not pointing to the same location.
Credential key repository is not setup correctly.
The credential Fernet key repository is expected to be readable by the user running keystone, but not world-readable, because it contains security sensitive secrets.
SQLite is not recommended for production deployments.
SQLite does not enforce type checking and has limited support for migrations, making it unsuitable for use in keystone. Please change your keystone.conf [database] connection value to point to a supported database driver, such as MySQL.
[saml] certfile should not contain a comma (,).
Because a comma is part of the API between keystone and the external xmlsec1 binary which utilizes the key, keystone cannot include a comma in the path to the private key file.
[saml] certfile should not contain a comma (,).
Because a comma is part of the API between keystone and the external xmlsec1 binary which utilizes the certificate, keystone cannot include a comma in the path to the public certificate file.
[ldap] group_members_are_ids is not enabled.
Because you’ve set keystone.conf [ldap] group_objectclass = posixGroup, we would have also expected you to enable set keystone.conf [ldap] group_members_are_ids because we suspect you’re using Open Directory, which would contain user ID’s in a posixGroup rather than LDAP DNs, as other object classes typically would.
Invalid password regular expression.
The password regular expression is invalid and users will not be able to make password changes until this has been corrected.
Ensure [security_compliance] password_regex is a valid regular expression.
Minimum password age should be less than the password expires days.
If the minimum password age is greater than or equal to the password expires days, then users would not be able to change their passwords before they expire.
Ensure [security_compliance] minimum_password_age is less than the [security_compliance] password_expires_days.
Password regular expression description is not set.
The password regular expression is set, but the description is not. Thus, if a user fails the password regular expression, they will not receive a message to explain why their requested password was insufficient.
Ensure [security_compliance] password_regex_description is set with a description of your password regular expression in a language for humans.
keystone.conf [DEFAULT] max_token_size should be adjusted.
This option is intended to protect keystone from unreasonably sized tokens, where “reasonable” is mostly dependent on the keystone.conf [token] provider that you’re using. If you’re using one of the following token providers, then you should set keystone.conf [DEFAULT] max_token_size accordingly:
Fernet key repository is empty.
After configuring keystone to use the Fernet token provider, you should use keystone-manage fernet_setup to initially populate your key repository with keys, and periodically rotate your keys with keystone-manage fernet_rotate.