The MySQL Keyring Similar adjustments are needed for applications that refer at runtime to  validate_password  plugin system and status variables. Change the no-dot plugin variable names to the corresponding dotted component variable names. UNINSTALL PLUGIN validate_password; If the  validate_password  plugin is loaded at server startup using a  --plugin-load  or  -- plugin-load-add  option, omit that option from the server startup procedure. For example, if the option is listed in a server option file, remove it from the file. MySQL Server supports a keyring that enables internal server components and plugins to securely store sensitive information for later retrieval. The implementation comprises these elements: 4. Uninstall the  validate_password  plugin: 5. Restart the server. 6.4.4 The MySQL Keyring •Keyring components and plugins that manage a backing store or communicate with a storage back end. Keyring use involves installing one from among the available components and plugins. Keyring components and plugins both manage keyring data but are configured differently and may have operational differences (see Section 6.4.4.1, “Keyring Components Versus Keyring Plugins” ). • component_keyring_file : Stores keyring data in a file local to the server host. Available in MySQL Community Edition and MySQL Enterprise Edition distributions as of MySQL 8.0.24. See Section 6.4.4.4, “Using the component_keyring_file File-Based Keyring Component” . • component_keyring_encrypted_file : Stores keyring data in an encrypted, password-protected file local to the server host. Available in MySQL Enterprise Edition distributions as of MySQL 8.0.24. See Section 6.4.4.5, “Using the component_keyring_encrypted_file Encrypted File-Based Keyring Component” . These keyring components are available: These keyring plugins are available: • keyring_file : Stores keyring data in a file local to the server host. Available in MySQL Community Edition and MySQL Enterprise Edition distributions. See Section 6.4.4.6, “Using the keyring_file File- Based Keyring Plugin” . • keyring_encrypted_file : Stores keyring data in an encrypted, password-protected file local to the server host. Available in MySQL Enterprise Edition distributions. See Section 6.4.4.7, “Using the keyring_encrypted_file Encrypted File-Based Keyring Plugin” . • keyring_okv : A KMIP 1.1 plugin for use with KMIP-compatible back end keyring storage products such as Oracle Key Vault and Gemalto SafeNet KeySecure Appliance. Available in MySQL Enterprise Edition distributions. See Section 6.4.4.8, “Using the keyring_okv KMIP Plugin” . • keyring_aws : Communicates with the Amazon Web Services Key Management Service for key generation and uses a local file for key storage. Available in MySQL Enterprise Edition distributions. See Section 6.4.4.9, “Using the keyring_aws Amazon Web Services Keyring Plugin” . • keyring_hashicorp : Communicates with HashiCorp Vault for back end storage. Available in MySQL Enterprise Edition distributions as of MySQL 8.0.18. See Section 6.4.4.10, “Using the HashiCorp Vault Keyring Plugin” . 1397