MySQL Bugs: #26160: migration of existing mysql network user credentials

Bug #26160	migration of existing mysql network user credentials
Submitted:	7 Feb 2007 19:52	Modified:	7 Mar 2007 20:21
Reporter:	Sloan Childers	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Enterprise Monitor: Installing	Severity:	S2 (Serious)
Version:		OS:
Assigned to:	Darren Oldag	CPU Architecture:	Any

Description:
Since we disabled allowing the user to specify network credentials at the user level (used to custom tailor news and alerts but not in the Merlin UI yet) we need to handle the migration case.

How to repeat:
Configure user specific network credentials and then upgrade to the 1.1 release which no longer supports this.

Suggested fix:
Remove the unused tables and associated code silently and ask for the global set during "first time setup"?  

or

Ask the user to migrate a set of the credentials to the global set during "first time setup" then remove the dead credentials?

We already will ask for global credentials if none exist.

Asking the user to migrate one of the existing set of credentials might represent a security issue, giving access to each set of credentials to the person doing the migration. On the other hand, we wouldn't display the password, just the email address. 

Nevertheless, I'm not excited about adding another fork to the licensing code to detect that there is at least one user level set of credentials and no server level and show some extra page that does that migration. Is there feedback on how a customer would react to re-entering a set of credentials to use an upgraded install?

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".