Joomla and MySQL 8 - Revision history

Cmb: Several markup and capitalization changes.

2022-11-27T22:42:04Z

Several markup and capitalization changes.

← Older revision		Revision as of 22:42, 27 November 2022
Line 1:		Line 1:
	<noinclude><languages /></noinclude>		<noinclude><languages /></noinclude>
	<translate>		<translate>
	==MySQL ~~default authentication plugin issue~~== <!--T:1-->		==MySQL Default Authentication Plugin Issue== <!--T:1-->
	</translate>		</translate>
	<translate><!--T:2--> It is possible to connect to a MySQL 8 Database using Joomla {{JVer\|3.x}}, however it requires a customisation on the MySQL 8 installation configuration. The reason is that MySQL 8 has ~~a lot of~~ low-level changes including the default authentication plugin changing to ~~<tt>~~sha256_password~~</tt>~~ from ~~<tt>~~mysql_native_password~~</tt>~~. The native PHP MySQL-Driver doesn't currently support MySQL 8 with this plugin. [https://github.com/php/php-src/commit/d6e81f0bfd0cb90586dd83d4fd47a4302605261a PHP 7.3 (alpha)] is supporting MySQL 8 though.</translate>		<translate><!--T:2--> It is possible to connect to a MySQL 8 Database using Joomla {{JVer\|3.x}}, however it requires a customisation on the MySQL 8 installation configuration. The reason is that MySQL 8 has many low-level changes including the default authentication plugin changing to ''sha256_password'' from ''mysql_native_password''. The native PHP MySQL-Driver doesn't currently support MySQL 8 with this plugin. [https://github.com/php/php-src/commit/d6e81f0bfd0cb90586dd83d4fd47a4302605261a PHP 7.3 (alpha)] is supporting MySQL 8 though.</translate>

	<translate>		<translate>
	==MySQL ~~configuration change~~ to ~~get~~ Joomla ~~working~~ with MySQL 8== <!--T:3-->		==MySQL Configuration Change to Get Joomla Working with MySQL 8== <!--T:3-->
	</translate>		</translate>
	<translate><!--T:4-->		<translate><!--T:4-->
	If you edit the configuration file for MySQL 8, you can change the default authentication plugin for MySQL to use the older mysql_native_password.		If you edit the configuration file for MySQL 8, you can change the default authentication plugin for MySQL to use the older ''mysql_native_password''.
	Open your configuration file ~~<tt>~~sudo nano /etc/my.cnf~~</tt>~~ (~~Please note~~ that your file may be under a different directory) ~~and add the following~~ configuration:</translate>		Open your configuration file ''sudo nano /etc/my.cnf''. (Note that your file may be under a different directory.) Add this configuration:</translate>
	<~~source~~ lang="ini">		<syntaxhighlight lang="ini">
	[mysqld]		[mysqld]
	default-authentication-plugin=mysql_native_password		default-authentication-plugin=mysql_native_password
	</~~source~~>		</syntaxhighlight>
	<translate><!--T:5--> If you don't have access to your config file ~~then~~ you can update your user ~~as follows~~:</translate>		<translate><!--T:5--> If you don't have access to your config file, you can update your user:</translate>
	<~~source~~ lang="mysql">		<syntaxhighlight lang="mysql">
	ALTER USER 'username'@'localhost' IDENTIFIED WITH mysql_native_password BY 'password';		ALTER USER 'username'@'localhost' IDENTIFIED WITH mysql_native_password BY 'password';
	</~~source~~>		</syntaxhighlight>
	<translate><!--T:6--> Replace username with the name of the user account and password with the password belonging to the account. Restart MySQL and you are done .~~..well~~, only if you have Joomla 3.8 or 3.9 installed.</translate>		<translate><!--T:6--> Replace ''username'' with the name of the user account and ''password'' with the password belonging to the account. Restart MySQL and you are done. Well, only if you have Joomla 3.8 or 3.9 installed.</translate>

	<translate>		<translate>
	==How MySQL ~~default authentication plugin works~~== <!--T:11-->		==How MySQL Default Authentication Plugin Works== <!--T:11-->
	</translate>		</translate>
	<translate><!--T:12--> The advantage of ~~<tt>~~mysql_native_password~~</tt>~~ is that it supports the challenge-response mechanism which is ~~very~~ quick and does not require encrypted connection. However, ~~<tt>~~mysql_native_password~~</tt>~~ relies on SHA1 algorithm and NIST has recommended to stop using it.</translate>		<translate><!--T:12--> The advantage of ''mysql_native_password'' is that it supports the challenge/response mechanism which is quick and does not require encrypted connection. However, ''mysql_native_password'' relies on SHA1 algorithm and NIST has recommended to stop using it.</translate>

			<translate><!--T:13--> Further, if two user accounts use the same password, ''mysql_native_password'' transformation is the same in the ''mysql.user'' table. Although the hash does not expose information about the actual password, it still tells which two users use the same password. To avoid that, a salt should be used. A salt is a random number that is used as one of the parameters to cryptographic hash functions used to transform user passwords. Since a salt is random and different for each execution, even if two users use the same passwords, the end result of transformation would look different.</translate>

	<translate><!--T:13--> Further, if two user accounts use the same password, <tt>mysql_native_password</tt> transformation is the same in the mysql.user table. Although the hash does not expose information about the actual password, it still tells which two users use the same password. To avoid that, a salt should be used. A salt is basically a random number that is used as one of the parameters to cryptographic hash functions used to transform user passwords. Since a salt is random and different for each execution, even if two users use the same passwords, the end result of transformation would look very different.</translate>
	<translate>		<translate>
	<!--T:14-->		<!--T:14-->
	Since MySQL 5.6, sha256_password authentication plugin is supported. It uses multiple rounds of SHA256 hash on a salted password to make sure that the hash transformation is more secure. However, it requires either encrypted connections or support for an RSA key pair. So, while password security is stronger, secure connections and multiple rounds of hash transformations require more time in the authentication process.</translate>		Since MySQL 5.6, the ''sha256_password'' authentication plugin is supported. It uses multiple rounds of SHA256 hash on a salted password to make sure that the hash transformation is more secure. However, it requires either encrypted connections or support for an RSA key pair. So, while password security is stronger, secure connections and multiple rounds of hash transformations require more time in the authentication process.</translate>

	<translate><!--T:15--> caching_sha2_password tries to combine the best of both worlds.</translate> <ref>https://mysqlserverteam.com/mysql-8-0-4-new-default-authentication-plugin-caching_sha2_password/</ref>		<translate><!--T:15--> The ''caching_sha2_password'' tries to combine the best of both worlds.</translate> <ref>https://mysqlserverteam.com/mysql-8-0-4-new-default-authentication-plugin-caching_sha2_password/</ref>

	<noinclude>		<noinclude>

Mfleeson: Update to rephrase, it is possible to connect, it's not a work-around just a configuration change in MySQL 8.

2021-05-20T11:32:38Z

Update to rephrase, it is possible to connect, it's not a work-around just a configuration change in MySQL 8.

← Older revision		Revision as of 11:32, 20 May 2021
Line 3:		Line 3:
	==MySQL default authentication plugin issue== <!--T:1-->		==MySQL default authentication plugin issue== <!--T:1-->
	</translate>		</translate>
	<translate><!--T:2--> It~~'s not~~ possible to connect to a MySQL 8 Database using Joomla {{JVer\|3.x}}. The reason is that MySQL 8 has a lot of changes ~~under the hood. One change that affects Joomla is~~ the default authentication plugin ~~which is~~ <tt>sha256_password</tt> ~~instead of~~ <tt>mysql_native_password</tt>. The native PHP MySQL-Driver ~~don~~'t support MySQL 8 with this plugin ~~yet other programming languages like GO or PERL are struggling too~~. [https://github.com/php/php-src/commit/d6e81f0bfd0cb90586dd83d4fd47a4302605261a PHP 7.3 (alpha)] is supporting MySQL 8 though.</translate>		<translate><!--T:2--> It is possible to connect to a MySQL 8 Database using Joomla {{JVer\|3.x}}, however it requires a customisation on the MySQL 8 installation configuration. The reason is that MySQL 8 has a lot of low-level changes including the default authentication plugin changing to <tt>sha256_password</tt> from <tt>mysql_native_password</tt>. The native PHP MySQL-Driver doesn't currently support MySQL 8 with this plugin. [https://github.com/php/php-src/commit/d6e81f0bfd0cb90586dd83d4fd47a4302605261a PHP 7.3 (alpha)] is supporting MySQL 8 though.</translate>

	<translate>		<translate>
	==~~Workaround~~ to get Joomla working with MySQL 8== <!--T:3-->		==MySQL configuration change to get Joomla working with MySQL 8== <!--T:3-->
	</translate>		</translate>
	<translate><!--T:4-->		<translate><!--T:4-->
	~~Fortunately there is a workaround! We~~ can ~~use~~ the ~~<tt>mysql_native_password</tt>~~ default authentication plugin for MySQL.		If you edit the configuration file for MySQL 8, you can change the default authentication plugin for MySQL to use the older mysql_native_password.
	~~We need to open our~~ configuration file <tt>sudo nano /etc/my.cnf</tt> (Please note that your file may be under a different directory) and add the following configuration:</translate>		Open your configuration file <tt>sudo nano /etc/my.cnf</tt> (Please note that your file may be under a different directory) and add the following configuration:</translate>
	<source lang="ini">		<source lang="ini">
	[mysqld]		[mysqld]

Wilsonge: Remove Joomla 4 stuff fixed in core

2019-11-02T23:54:30Z

Remove Joomla 4 stuff fixed in core

← Older revision		Revision as of 23:54, 2 November 2019
Line 3:		Line 3:
	==MySQL default authentication plugin issue== <!--T:1-->		==MySQL default authentication plugin issue== <!--T:1-->
	</translate>		</translate>
	<translate><!--T:2--> It's not possible to connect to a MySQL 8 Database using Joomla 3.~~8, 3.9 or 4.0~~. The reason is that MySQL 8 has a lot of changes under the hood. One change that affects Joomla is the default authentication plugin which is <tt>sha256_password</tt> instead of <tt>mysql_native_password</tt>. The native PHP MySQL-Driver don't support MySQL 8 with this plugin yet other programming languages like GO or PERL are struggling too. [https://github.com/php/php-src/commit/d6e81f0bfd0cb90586dd83d4fd47a4302605261a PHP 7.3 (alpha)] is supporting MySQL 8 though.</translate>		<translate><!--T:2--> It's not possible to connect to a MySQL 8 Database using Joomla {{JVer\|3.x}}. The reason is that MySQL 8 has a lot of changes under the hood. One change that affects Joomla is the default authentication plugin which is <tt>sha256_password</tt> instead of <tt>mysql_native_password</tt>. The native PHP MySQL-Driver don't support MySQL 8 with this plugin yet other programming languages like GO or PERL are struggling too. [https://github.com/php/php-src/commit/d6e81f0bfd0cb90586dd83d4fd47a4302605261a PHP 7.3 (alpha)] is supporting MySQL 8 though.</translate>

	<translate>		<translate>
Line 20:		Line 20:
	</source>		</source>
	<translate><!--T:6--> Replace username with the name of the user account and password with the password belonging to the account. Restart MySQL and you are done ...well, only if you have Joomla 3.8 or 3.9 installed.</translate>		<translate><!--T:6--> Replace username with the name of the user account and password with the password belonging to the account. Restart MySQL and you are done ...well, only if you have Joomla 3.8 or 3.9 installed.</translate>

	~~<translate><!--T:7--> If you want to work with Joomla 4.0, you have to do some extra work, because the administration dashboard is blank after the installation with Joomla 4.0 and MySQL 8.</translate>~~

	~~<translate><!--T:8-->~~
	~~Fortunately there is a fix for that too!~~
	~~MySQL 8 is returning <tt>Incorrect date value: '0000-00-00'</tt> after running following insertion from the installation file <tt>/installation/sql/mysql/joomla.sql</tt>.</translate>~~

	~~<translate><!--T:9--> The following query must be run to fix this. Replace #_ with your table prefix.</translate>~~
	~~<source lang=sql>~~
	~~UPDATE `#__modules` SET `checked_out_time` = '1000-01-01 00:00:00', `publish_up` = '1000-01-01 00:00:00', `publish_down` = '1000-01-01 00:00:00';~~
	~~</source>~~

	~~<translate><!--T:10--> This is happening because since MySQL 5.7, MySQL stops supporting zeros value in date / datetime.</translate>~~

	<translate>		<translate>

Mickmackusa: improved English

2019-10-19T06:00:34Z

improved English

← Older revision		Revision as of 06:00, 19 October 2019
Line 19:		Line 19:
	ALTER USER 'username'@'localhost' IDENTIFIED WITH mysql_native_password BY 'password';		ALTER USER 'username'@'localhost' IDENTIFIED WITH mysql_native_password BY 'password';
	</source>		</source>
	<translate><!--T:6--> Replace username with the name of the user account and password with the password belonging to the account. Restart MySQL and you are done, ~~well~~ only if you have Joomla 3.8 or 3.9 installed.</translate>		<translate><!--T:6--> Replace username with the name of the user account and password with the password belonging to the account. Restart MySQL and you are done ...well, only if you have Joomla 3.8 or 3.9 installed.</translate>

	<translate><!--T:7--> If you want to work with Joomla 4.0 you have to do some extra work, because the administration dashboard is blank after the installation with Joomla 4.0 and MySQL 8.</translate>		<translate><!--T:7--> If you want to work with Joomla 4.0, you have to do some extra work, because the administration dashboard is blank after the installation with Joomla 4.0 and MySQL 8.</translate>

	<translate><!--T:8-->		<translate><!--T:8-->
Line 37:		Line 37:
	==How MySQL default authentication plugin works== <!--T:11-->		==How MySQL default authentication plugin works== <!--T:11-->
	</translate>		</translate>
	<translate><!--T:12--> The advantage of <tt>mysql_native_password</tt> is that it supports challenge-response mechanism which is very quick and does not require encrypted connection. However, <tt>mysql_native_password</tt> relies on SHA1 algorithm and NIST has ~~suggested~~ to stop using it.</translate>		<translate><!--T:12--> The advantage of <tt>mysql_native_password</tt> is that it supports the challenge-response mechanism which is very quick and does not require encrypted connection. However, <tt>mysql_native_password</tt> relies on SHA1 algorithm and NIST has recommended to stop using it.</translate>

	<translate><!--T:13--> Further, if two user accounts use the same password, <tt>mysql_native_password</tt> transformation is the same in the mysql.user table. Although the hash does not expose information about the actual password, it still tells which two users use the same password. To avoid that, salt should be used. ~~Salt~~ is basically a random number that is used as one of the ~~inputs~~ to cryptographic hash functions used to transform user passwords. Since salt is random and different for each execution, even if two users use the same passwords, the end result of transformation would look very different.</translate>		<translate><!--T:13--> Further, if two user accounts use the same password, <tt>mysql_native_password</tt> transformation is the same in the mysql.user table. Although the hash does not expose information about the actual password, it still tells which two users use the same password. To avoid that, a salt should be used. A salt is basically a random number that is used as one of the parameters to cryptographic hash functions used to transform user passwords. Since a salt is random and different for each execution, even if two users use the same passwords, the end result of transformation would look very different.</translate>
	<translate>		<translate>
	<!--T:14-->		<!--T:14-->

Sandra97: Marked this version for translation

2018-08-01T14:22:08Z

Marked this version for translation

← Older revision		Revision as of 14:22, 1 August 2018
Line 1:		Line 1:
	<noinclude><languages /></noinclude>		<noinclude><languages /></noinclude>
	<translate>		<translate>
	==MySQL default authentication plugin issue==		==MySQL default authentication plugin issue== <!--T:1-->
	</translate>		</translate>
	<translate>It's not possible to connect to a MySQL 8 Database using Joomla 3.8, 3.9 or 4.0. The reason is that MySQL 8 has a lot of changes under the hood. One change that affects Joomla is the default authentication plugin which is <tt>sha256_password</tt> instead of <tt>mysql_native_password</tt>. The native PHP MySQL-Driver don't support MySQL 8 with this plugin yet other programming languages like GO or PERL are struggling too. [https://github.com/php/php-src/commit/d6e81f0bfd0cb90586dd83d4fd47a4302605261a PHP 7.3 (alpha)] is supporting MySQL 8 though.</translate>		<translate><!--T:2--> It's not possible to connect to a MySQL 8 Database using Joomla 3.8, 3.9 or 4.0. The reason is that MySQL 8 has a lot of changes under the hood. One change that affects Joomla is the default authentication plugin which is <tt>sha256_password</tt> instead of <tt>mysql_native_password</tt>. The native PHP MySQL-Driver don't support MySQL 8 with this plugin yet other programming languages like GO or PERL are struggling too. [https://github.com/php/php-src/commit/d6e81f0bfd0cb90586dd83d4fd47a4302605261a PHP 7.3 (alpha)] is supporting MySQL 8 though.</translate>

	<translate>		<translate>
	==Workaround to get Joomla working with MySQL 8==		==Workaround to get Joomla working with MySQL 8== <!--T:3-->
	</translate>		</translate>
	<translate>Fortunately there is a workaround! We can use the <tt>mysql_native_password</tt> default authentication plugin for MySQL.		<translate><!--T:4-->
			Fortunately there is a workaround! We can use the <tt>mysql_native_password</tt> default authentication plugin for MySQL.
	We need to open our configuration file <tt>sudo nano /etc/my.cnf</tt> (Please note that your file may be under a different directory) and add the following configuration:</translate>		We need to open our configuration file <tt>sudo nano /etc/my.cnf</tt> (Please note that your file may be under a different directory) and add the following configuration:</translate>
	<source lang="ini">		<source lang="ini">
Line 14:		Line 15:
	default-authentication-plugin=mysql_native_password		default-authentication-plugin=mysql_native_password
	</source>		</source>
	<translate>If you don't have access to your config file then you can update your user as follows:</translate>		<translate><!--T:5--> If you don't have access to your config file then you can update your user as follows:</translate>
	<source lang="mysql">		<source lang="mysql">
	ALTER USER 'username'@'localhost' IDENTIFIED WITH mysql_native_password BY 'password';		ALTER USER 'username'@'localhost' IDENTIFIED WITH mysql_native_password BY 'password';
	</source>		</source>
	<translate>Replace username with the name of the user account and password with the password belonging to the account. Restart MySQL and you are done, well only if you have Joomla 3.8 or 3.9 installed.</translate>		<translate><!--T:6--> Replace username with the name of the user account and password with the password belonging to the account. Restart MySQL and you are done, well only if you have Joomla 3.8 or 3.9 installed.</translate>

	<translate>If you want to work with Joomla 4.0 you have to do some extra work, because the administration dashboard is blank after the installation with Joomla 4.0 and MySQL 8.</translate>		<translate><!--T:7--> If you want to work with Joomla 4.0 you have to do some extra work, because the administration dashboard is blank after the installation with Joomla 4.0 and MySQL 8.</translate>

	<translate>Fortunately there is a fix for that too!		<translate><!--T:8-->
			Fortunately there is a fix for that too!
	MySQL 8 is returning <tt>Incorrect date value: '0000-00-00'</tt> after running following insertion from the installation file <tt>/installation/sql/mysql/joomla.sql</tt>.</translate>		MySQL 8 is returning <tt>Incorrect date value: '0000-00-00'</tt> after running following insertion from the installation file <tt>/installation/sql/mysql/joomla.sql</tt>.</translate>

	<translate>The following query must be run to fix this. Replace #_ with your table prefix.</translate>		<translate><!--T:9--> The following query must be run to fix this. Replace #_ with your table prefix.</translate>
	<source lang=sql>		<source lang=sql>
	UPDATE `#__modules` SET `checked_out_time` = '1000-01-01 00:00:00', `publish_up` = '1000-01-01 00:00:00', `publish_down` = '1000-01-01 00:00:00';		UPDATE `#__modules` SET `checked_out_time` = '1000-01-01 00:00:00', `publish_up` = '1000-01-01 00:00:00', `publish_down` = '1000-01-01 00:00:00';
	</source>		</source>

	<translate>This is happening because since MySQL 5.7, MySQL stops supporting zeros value in date / datetime.</translate>		<translate><!--T:10--> This is happening because since MySQL 5.7, MySQL stops supporting zeros value in date / datetime.</translate>

	<translate>		<translate>
	==How MySQL default authentication plugin works==		==How MySQL default authentication plugin works== <!--T:11-->
	</translate>		</translate>
	<translate>The advantage of <tt>mysql_native_password</tt> is that it supports challenge-response mechanism which is very quick and does not require encrypted connection. However, <tt>mysql_native_password</tt> relies on SHA1 algorithm and NIST has suggested to stop using it.</translate>		<translate><!--T:12--> The advantage of <tt>mysql_native_password</tt> is that it supports challenge-response mechanism which is very quick and does not require encrypted connection. However, <tt>mysql_native_password</tt> relies on SHA1 algorithm and NIST has suggested to stop using it.</translate>

	<translate>Further, if two user accounts use the same password, <tt>mysql_native_password</tt> transformation is the same in the mysql.user table. Although the hash does not expose information about the actual password, it still tells which two users use the same password. To avoid that, salt should be used. Salt is basically a random number that is used as one of the inputs to cryptographic hash functions used to transform user passwords. Since salt is random and different for each execution, even if two users use the same passwords, the end result of transformation would look very different.</translate>		<translate><!--T:13--> Further, if two user accounts use the same password, <tt>mysql_native_password</tt> transformation is the same in the mysql.user table. Although the hash does not expose information about the actual password, it still tells which two users use the same password. To avoid that, salt should be used. Salt is basically a random number that is used as one of the inputs to cryptographic hash functions used to transform user passwords. Since salt is random and different for each execution, even if two users use the same passwords, the end result of transformation would look very different.</translate>
	<translate>		<translate>
			<!--T:14-->
	Since MySQL 5.6, sha256_password authentication plugin is supported. It uses multiple rounds of SHA256 hash on a salted password to make sure that the hash transformation is more secure. However, it requires either encrypted connections or support for an RSA key pair. So, while password security is stronger, secure connections and multiple rounds of hash transformations require more time in the authentication process.</translate>		Since MySQL 5.6, sha256_password authentication plugin is supported. It uses multiple rounds of SHA256 hash on a salted password to make sure that the hash transformation is more secure. However, it requires either encrypted connections or support for an RSA key pair. So, while password security is stronger, secure connections and multiple rounds of hash transformations require more time in the authentication process.</translate>

	<translate>caching_sha2_password tries to combine the best of both worlds.</translate> <ref>https://mysqlserverteam.com/mysql-8-0-4-new-default-authentication-plugin-caching_sha2_password/</ref>		<translate><!--T:15--> caching_sha2_password tries to combine the best of both worlds.</translate> <ref>https://mysqlserverteam.com/mysql-8-0-4-new-default-authentication-plugin-caching_sha2_password/</ref>

	<noinclude>		<noinclude>

Sandra97: Marked for translation

2018-08-01T14:21:58Z

Marked for translation

← Older revision		Revision as of 14:21, 1 August 2018
Line 1:		Line 1:
			<noinclude><languages /></noinclude>
			<translate>
	==MySQL default authentication plugin issue==		==MySQL default authentication plugin issue==
	It's not possible to connect to a MySQL 8 Database using Joomla 3.8, 3.9 or 4.0. The reason is that MySQL 8 has a lot of changes under the hood. One change that affects Joomla is the default authentication plugin which is <tt>sha256_password</tt> instead of <tt>mysql_native_password</tt>. The native PHP MySQL-Driver don't support MySQL 8 with this plugin yet other programming languages like GO or PERL are struggling too. [https://github.com/php/php-src/commit/d6e81f0bfd0cb90586dd83d4fd47a4302605261a PHP 7.3 (alpha)] is supporting MySQL 8 though.		</translate>
			<translate>It's not possible to connect to a MySQL 8 Database using Joomla 3.8, 3.9 or 4.0. The reason is that MySQL 8 has a lot of changes under the hood. One change that affects Joomla is the default authentication plugin which is <tt>sha256_password</tt> instead of <tt>mysql_native_password</tt>. The native PHP MySQL-Driver don't support MySQL 8 with this plugin yet other programming languages like GO or PERL are struggling too. [https://github.com/php/php-src/commit/d6e81f0bfd0cb90586dd83d4fd47a4302605261a PHP 7.3 (alpha)] is supporting MySQL 8 though.</translate>

			<translate>
	==Workaround to get Joomla working with MySQL 8==		==Workaround to get Joomla working with MySQL 8==
	Fortunately there is a workaround! We can use the <tt>mysql_native_password</tt> default authentication plugin for MySQL.		</translate>
	We need to open our configuration file <tt>sudo nano /etc/my.cnf</tt> (Please note that your file may be under a different directory) and add the following configuration:		<translate>Fortunately there is a workaround! We can use the <tt>mysql_native_password</tt> default authentication plugin for MySQL.
			We need to open our configuration file <tt>sudo nano /etc/my.cnf</tt> (Please note that your file may be under a different directory) and add the following configuration:</translate>
	<source lang="ini">		<source lang="ini">
	[mysqld]		[mysqld]
	default-authentication-plugin=mysql_native_password		default-authentication-plugin=mysql_native_password
	</source>		</source>
	If you don't have access to your config file then you can update your user as follows:		<translate>If you don't have access to your config file then you can update your user as follows:</translate>
	<source lang="mysql">		<source lang="mysql">
	ALTER USER 'username'@'localhost' IDENTIFIED WITH mysql_native_password BY 'password';		ALTER USER 'username'@'localhost' IDENTIFIED WITH mysql_native_password BY 'password';
	</source>		</source>
	Replace username with the name of the user account and password with the password belonging to the account. Restart MySQL and you are done, well only if you have Joomla 3.8 or 3.9 installed.		<translate>Replace username with the name of the user account and password with the password belonging to the account. Restart MySQL and you are done, well only if you have Joomla 3.8 or 3.9 installed.</translate>

	If you want to work with Joomla 4.0 you have to do some extra work, because the administration dashboard is blank after the installation with Joomla 4.0 and MySQL 8.		<translate>If you want to work with Joomla 4.0 you have to do some extra work, because the administration dashboard is blank after the installation with Joomla 4.0 and MySQL 8.</translate>

	Fortunately there is a fix for that too!		<translate>Fortunately there is a fix for that too!
	MySQL 8 is returning <tt>Incorrect date value: '0000-00-00'</tt> after running following insertion from the installation file <tt>/installation/sql/mysql/joomla.sql</tt>.		MySQL 8 is returning <tt>Incorrect date value: '0000-00-00'</tt> after running following insertion from the installation file <tt>/installation/sql/mysql/joomla.sql</tt>.</translate>

	The following query must be run to fix this. Replace #_ with your table prefix.		<translate>The following query must be run to fix this. Replace #_ with your table prefix.</translate>
	<source lang=sql>		<source lang=sql>
	UPDATE `#__modules` SET `checked_out_time` = '1000-01-01 00:00:00', `publish_up` = '1000-01-01 00:00:00', `publish_down` = '1000-01-01 00:00:00';		UPDATE `#__modules` SET `checked_out_time` = '1000-01-01 00:00:00', `publish_up` = '1000-01-01 00:00:00', `publish_down` = '1000-01-01 00:00:00';
	</source>		</source>

	This is happening because since MySQL 5.7, MySQL stops supporting zeros value in date / datetime.		<translate>This is happening because since MySQL 5.7, MySQL stops supporting zeros value in date / datetime.</translate>

			<translate>
	==How MySQL default authentication plugin works==		==How MySQL default authentication plugin works==
	The advantage of <tt>mysql_native_password</tt> is that it supports challenge-response mechanism which is very quick and does not require encrypted connection. However, <tt>mysql_native_password</tt> relies on SHA1 algorithm and NIST has suggested to stop using it.		</translate>
			<translate>The advantage of <tt>mysql_native_password</tt> is that it supports challenge-response mechanism which is very quick and does not require encrypted connection. However, <tt>mysql_native_password</tt> relies on SHA1 algorithm and NIST has suggested to stop using it.</translate>

	Further, if two user accounts use the same password, <tt>mysql_native_password</tt> transformation is the same in the mysql.user table. Although the hash does not expose information about the actual password, it still tells which two users use the same password. To avoid that, salt should be used. Salt is basically a random number that is used as one of the inputs to cryptographic hash functions used to transform user passwords. Since salt is random and different for each execution, even if two users use the same passwords, the end result of transformation would look very different.		<translate>Further, if two user accounts use the same password, <tt>mysql_native_password</tt> transformation is the same in the mysql.user table. Although the hash does not expose information about the actual password, it still tells which two users use the same password. To avoid that, salt should be used. Salt is basically a random number that is used as one of the inputs to cryptographic hash functions used to transform user passwords. Since salt is random and different for each execution, even if two users use the same passwords, the end result of transformation would look very different.</translate>
			<translate>
			Since MySQL 5.6, sha256_password authentication plugin is supported. It uses multiple rounds of SHA256 hash on a salted password to make sure that the hash transformation is more secure. However, it requires either encrypted connections or support for an RSA key pair. So, while password security is stronger, secure connections and multiple rounds of hash transformations require more time in the authentication process.</translate>

	Since MySQL 5.6, sha256_password authentication plugin is supported. It uses multiple rounds of SHA256 hash on a salted password to make sure that the hash transformation is more secure. However, it requires either encrypted connections or support for an RSA key pair. So, while password security is stronger, secure connections and multiple rounds of hash transformations require more time in the authentication process.		<translate>caching_sha2_password tries to combine the best of both worlds.</translate> <ref>https://mysqlserverteam.com/mysql-8-0-4-new-default-authentication-plugin-caching_sha2_password/</ref>

	caching_sha2_password tries to combine the best of both worlds. <ref>https://mysqlserverteam.com/mysql-8-0-4-new-default-authentication-plugin-caching_sha2_password/</ref>

	<noinclude>		<noinclude>
	[[Category:Server configurations]]		[[Category:Server configurations{{#translation:}}]]
	[[Category:Installation]]		[[Category:Installation{{#translation:}}]]
	[[Category:Tutorials]]		[[Category:Tutorials{{#translation:}}]]
	</noinclude>		</noinclude>

Bilalreffas: /* Workaround to get Joomla working with MySQL 8 */

2018-08-01T13:07:00Z

Workaround to get Joomla working with MySQL 8

← Older revision		Revision as of 13:07, 1 August 2018
Line 20:		Line 20:
	MySQL 8 is returning <tt>Incorrect date value: '0000-00-00'</tt> after running following insertion from the installation file <tt>/installation/sql/mysql/joomla.sql</tt>.		MySQL 8 is returning <tt>Incorrect date value: '0000-00-00'</tt> after running following insertion from the installation file <tt>/installation/sql/mysql/joomla.sql</tt>.

	The following ~~querie~~ must be run to fix this. Replace #_ with your table prefix.		The following query must be run to fix this. Replace #_ with your table prefix.
	<source lang=sql>		<source lang=sql>
	UPDATE `#__modules` SET `checked_out_time` = '1000-01-01 00:00:00', `publish_up` = '1000-01-01 00:00:00', `publish_down` = '1000-01-01 00:00:00';		UPDATE `#__modules` SET `checked_out_time` = '1000-01-01 00:00:00', `publish_up` = '1000-01-01 00:00:00', `publish_down` = '1000-01-01 00:00:00';

Bilalreffas: /* Workaround to get Joomla working with MySQL 8 */

2018-08-01T12:45:43Z

Workaround to get Joomla working with MySQL 8

← Older revision		Revision as of 12:45, 1 August 2018
Line 20:		Line 20:
	MySQL 8 is returning <tt>Incorrect date value: '0000-00-00'</tt> after running following insertion from the installation file <tt>/installation/sql/mysql/joomla.sql</tt>.		MySQL 8 is returning <tt>Incorrect date value: '0000-00-00'</tt> after running following insertion from the installation file <tt>/installation/sql/mysql/joomla.sql</tt>.

	The following ~~queries~~ must be run to fix this. Replace #_ with your table prefix.		The following querie must be run to fix this. Replace #_ with your table prefix.
	<source lang=sql>		<source lang=sql>
	UPDATE `#__modules` SET `checked_out_time` = '1000-01-01 00:00:00', `publish_up` = '1000-01-01 00:00:00', `publish_down` = '1000-01-01 00:00:00';		UPDATE `#__modules` SET `checked_out_time` = '1000-01-01 00:00:00', `publish_up` = '1000-01-01 00:00:00', `publish_down` = '1000-01-01 00:00:00';

Rolandd: Fixed query

2018-08-01T07:33:15Z

Fixed query

← Older revision		Revision as of 07:33, 1 August 2018
Line 20:		Line 20:
	MySQL 8 is returning <tt>Incorrect date value: '0000-00-00'</tt> after running following insertion from the installation file <tt>/installation/sql/mysql/joomla.sql</tt>.		MySQL 8 is returning <tt>Incorrect date value: '0000-00-00'</tt> after running following insertion from the installation file <tt>/installation/sql/mysql/joomla.sql</tt>.

	The following queries must be run to fix this.		The following queries must be run to fix this. Replace #_ with your table prefix.
	<source lang=sql>		<source lang=sql>
	UPDATE `#__modules` SET `checked_out_time` = '~~1001~~-01-01 00:00:00', `publish_up` = '~~1001~~-01-01 00:00:00', `publish_down` = '~~1001~~-01-01 00:00:00';		UPDATE `#__modules` SET `checked_out_time` = '1000-01-01 00:00:00', `publish_up` = '1000-01-01 00:00:00', `publish_down` = '1000-01-01 00:00:00';
	</source>		</source>

Rolandd: Add blank line

2018-08-01T07:23:52Z

Add blank line

← Older revision		Revision as of 07:23, 1 August 2018
Line 18:		Line 18:

	Fortunately there is a fix for that too!		Fortunately there is a fix for that too!
	MySQL 8 is returning <tt>Incorrect date value: '0000-00-00'</tt> after running following insertion from the installation file <tt>/installation/sql/mysql/joomla.sql</tt>. The following queries must be run to fix this.		MySQL 8 is returning <tt>Incorrect date value: '0000-00-00'</tt> after running following insertion from the installation file <tt>/installation/sql/mysql/joomla.sql</tt>.

			The following queries must be run to fix this.
	<source lang=sql>		<source lang=sql>
	UPDATE `#__modules` SET `checked_out_time` = '1001-01-01 00:00:00', `publish_up` = '1001-01-01 00:00:00', `publish_down` = '1001-01-01 00:00:00';		UPDATE `#__modules` SET `checked_out_time` = '1001-01-01 00:00:00', `publish_up` = '1001-01-01 00:00:00', `publish_down` = '1001-01-01 00:00:00';