Documentation Home
MySQL 9.4 Reference Manual
Related Documentation Download this Manual
PDF (US Ltr) - 41.2Mb
PDF (A4) - 41.3Mb
Man Pages (TGZ) - 262.8Kb
Man Pages (Zip) - 368.8Kb
Info (Gzip) - 4.1Mb
Info (Zip) - 4.1Mb


MySQL 9.4 Reference Manual  / ...  / Security  / Security Components and Plugins  / The Password Validation Component  /  Password Validation Component Installation and Uninstallation

8.4.4.1 Password Validation Component Installation and Uninstallation

This section describes how to install and uninstall thevalidate_password password-validation component. For general information about installing and uninstalling components, seeSection 7.5, “MySQL Components”.

Note

If you install MySQL 9.4 using theMySQL Yum repository,MySQL SLES Repository, orRPM packages provided by Oracle, thevalidate_password component is enabled by default after you start your MySQL Server for the first time.

Upgrades to MySQL 9.4 from 9.3 using Yum or RPM packages leave thevalidate_password plugin in place. To make the transition from thevalidate_password plugin to thevalidate_password component, seeSection 8.4.4.3, “Transitioning to the Password Validation Component”.

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

To install thevalidate_password component, use this statement:

INSTALL COMPONENT 'file://component_validate_password';

Component installation is a one-time operation that need not be done per server startup.INSTALL COMPONENT loads the component, and also registers it in themysql.component system table to cause it to be loaded during subsequent server startups.

To uninstall thevalidate_password component, use this statement:

UNINSTALL COMPONENT 'file://component_validate_password';

UNINSTALL COMPONENT unloads the component, and unregisters it from themysql.component system table to cause it not to be loaded during subsequent server startups.