Bug #89945 Make default_authentication_plugin setting dynamic
Submitted: 7 Mar 2018 13:12 Modified: 12 Mar 2018 7:26
Reporter: Simon Mudd (OCA) Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Server: Pluggable Authentication Severity:S4 (Feature request)
Version:8.0..4 OS:Any
Assigned to: CPU Architecture:Any
Tags: configuration, default_authentication_plugin, dynamic, easy management

[7 Mar 2018 13:12] Simon Mudd
Description:
Default authentication in 8.0 is not dynamic. That is not very helpful.

I may need to support old applications with the native mysql password authentication schema for compatibility thus setting default_authentication_plugin = 'mysql_native_password' while migrating from running 5.7 to 8.0 may make sense.

However, when I've upgraded all servers to 8.0 I may want to change this setting back to the "better" caching_sha2 setting.

Checking what happens when I try to change the default setting I see:

`ERROR 1238 (HY000): Variable 'default_authentication_plugin' is a read only variable`

This requires me to restart mysqld. That is not convenient.

Just because a setting like this doesn’t change much doesn’t mean that it shouldn’t be dynamic.

How to repeat:
See above.

Suggested fix:
Please make this setting dynamic to avoid the need to restart mysqld.
[7 Mar 2018 13:23] Simon Mudd
Current example of an application that can't handle this is orchestrator as I think the go driver that's being used is still unaware of the new authentication method.

I believe there is an issue on the driver's site: https://github.com/go-sql-driver/mysql/issues but haven't checked (recently).

This is not to single out this driver specifically. I'm sure that several drivers not maintained by Oracle directly may need to be updated and that may take some time.
[7 Mar 2018 13:25] Simon Mudd
Go driver issue can be found at: https://github.com/go-sql-driver/mysql/issues/625
[7 Mar 2018 16:38] Daniël van Eeden
This is a duplicate of:
Bug #89573 	default_authentication_plugin should be dynamic
[12 Mar 2018 7:26] MySQL Verification Team
Hello Simon,

Thank you for the feature request!
This is duplicate of Bug#89573.

Thanks,
Umesh