Bug #70745 Add authentication plugin info to mysqluserclone
Submitted: 27 Oct 2013 20:31 Modified: 4 Aug 2016 19:57
Reporter: Daniël van Eeden (OCA) Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Utilities Severity:S2 (Serious)
Version:1.2.3, 1.3.5 OS:Any
Assigned to: CPU Architecture:Any

[27 Oct 2013 20:31] Daniël van Eeden
Description:
When mysqluserclone dumps (or copies?) a user which used the PAM plugin then the authentication plugin setting is not shown. 

See also: Bug #70744

How to repeat:
CREATE USER 'dveeden'@'localhost' IDENTIFIED WITH authentication_pam;

mysqluserclone.py  --source=user:pwd@host -d 'dveeden'@'localhost'
# Source on 127.0.0.1: ... connected.
# Dumping grants for user dveeden@localhost
GRANT USAGE ON *.* TO 'dveeden'@'localhost'

Suggested fix:
Make sure to include IDENTIFIED WITH in the output if an authentication plugin is used for that user.
[28 Oct 2013 5:05] MySQL Verification Team
Hello Daniel,

Thank you for the bug report.
Verified as described.

Thanks,
Umesh
[3 Feb 2015 14:58] Daniël van Eeden
If RFE Bug #27761 gets implemented the results of this bug would be less severe.
[4 Aug 2016 19:57] Philip Olson
Posted by developer:
 
Fixed as of the upcoming MySQL Utilities 1.6.4 release, and here's the changelog entry:

Corrected an issue when copying users that were created with the
"IDENTIFIED WITH" authentication plugin option. The utility would copy the
user, but not copy the authentication plugin setting, making it impossible
to copy users with the plugin. The utility now captures the plugin name
and assigns it to the new user. An error is thrown if the plugin is not on
the destination machine or is inactive. A warning is also issued if the
user attempts to assign a password to a new user when the source user has
an authentication plugin. In this case, the utility will use the password
and not the authentication plugin for the new user.

Thank you for the bug report.