content_image/844167.jpg content_image/844166.jpg
For information about using the keyring functions, see Section 6.4.4.14, “General-Purpose Keyring Key- Management Functions” . 

Keyring components, plugins, and functions access a keyring service that provides the interface to the keyring. For information about accessing this service and writing keyring plugins, see Section 5.6.9.2, “The Keyring Service” , and Writing Keyring Plugins. 

## 6.4.4.1 Keyring Components Versus Keyring Plugins 

The MySQL Keyring originally implemented keystore capabilities using server plugins, but began transitioning to use the component infrastructure in MySQL 8.0.24. This section briefly compares keyring components and plugins to provide an overview of their differences. It may assist you in making the transition from plugins to components, or, if you are just beginning to use the keyring, assist you in choosing whether to use a component versus using a plugin. 

•Keyring plugin loading uses the --early-plugin-load  option. Keyring component loading uses a manifest. 

•Keyring plugin configuration is based on plugin-specific system variables. For keyring components, no system variables are used. Instead, each component has its own configuration file. 

•Keyring components have fewer restrictions than keyring plugins with respect to key types and lengths. See Section 6.4.4.12, “Supported Keyring Key Types and Lengths” . 

## 6.4.4.2 Keyring Component Installation 

Keyring service consumers require that a keyring component or plugin be installed: 

•To use a keyring component, begin with the instructions here. 

•To use a keyring plugin instead, begin with Section 6.4.4.3, “Keyring Plugin Installation” . 

•If you intend to use keyring functions in conjunction with the chosen keyring component or plugin, install the functions after installing that component or plugin, using the instructions in Section 6.4.4.14, “General-Purpose Keyring Key-Management Functions” . 

<img src='content_image/844167.jpg'>

MySQL provides these keyring component choices: 

<img src='content_image/844166.jpg'>

## Note 

Only one keyring component or plugin should be enabled at a time. Enabling multiple keyring components or plugins is unsupported and results may not be as anticipated. 

• component_keyring_file : Stores keyring data in a file local to the server host. Available in MySQL Community Edition and MySQL Enterprise Edition distributions. 

• component_keyring_encrypted_file : Stores keyring data in an encrypted, password-protected file local to the server host. Available in MySQL Enterprise Edition distributions. 

To be usable by the server, the component library file must be located in the MySQL plugin directory (the directory named by the plugin_dir  system variable). If necessary, configure the plugin directory location by setting the value of plugin_dir  at server startup. 

A keyring component or plugin must be loaded early during the server startup sequence so that other components can access it as necessary during their own initialization. For example, the InnoDB  storage 

