MySQL Bugs: #30848: Bad Key Prevents You From Accessing Product To Update Key

Bug #30848	Bad Key Prevents You From Accessing Product To Update Key
Submitted:	6 Sep 2007 0:28	Modified:	24 Jul 2008 14:22
Reporter:	Joshua Ganderson	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Enterprise Monitor: Web	Severity:	S2 (Serious)
Version:		OS:	Any
Assigned to:	Mark Matthews	CPU Architecture:	Any
Tags:	mer 121

Description:
If you have an old format key, there may be a parse error trying to instantiate the account information (see issue https://support.mysql.com/view.php?id=19128).

How to repeat:
Install a very old product key.
Restart tomcat.
Try to log in.

Suggested fix:
Catch this failure and treat it as a setup failure. Force the user to go to the setup process.

Workaround: download newer key

to make this easier on the customer, we could allow the setup page to be run again manually

Having manual access is an option but it would break all of the current logic for setup (hiding completed/validated steps and sending the user on if no necessary steps were found). My original suggestion would be much simpler and more stable. Not only that, we introduce a security risk if you can access the setup process after the product has been collecting data for some time. Remember, this allows you to create a new administrator without having to log in.

Workaround:
delete from properties where property='license';
restart tomcat
user is taken to setup page on trying to access merlin
put in new key

We're losing track of this by not having it assigned to anyone, so I'm assigning to Josh since the last question was for him.

will check with bill to see if a real problem and for when. will fix for RC. btw, we don't change format between 1.3 and 2.0 so failure would be earlier up the chain.

Since we haven't received a lot of complaints from people about "bad" keys, I'm thinking this key could have been generated while things were in flux. Therefore, I'm setting this to Documenting in case anyone else has the same problem and needs to see the workaround. Btw, here is the workaround taken from an email from Adam:

 Generate your key XML data;
 https://enterprise.mysql.com/monitoring/generate_key.php?version=1.2

 Stop Tomcat;
 /opt/mysql/network/monitoring/mysqlnetworkctl.sh stop tomcat

 cd /opt/mysql/network/monitoring
 cat configuration_report.txt
 mysql -uservice_manager -ppassword -P13306 -S mysql/tmp/mysql.sock merlin

 mysql> update properties set value='<key>' where property='license';
 (Please include the entire XML output obtained from the key generation
 in-place of <key>)

 Start Tomcat;
 /opt/mysql/network/monitoring/mysqlnetworkctl.sh stop tomcat

 Re-Attempt to access the dashboard.

Closing. Work around was documented by Peter Lavin as a known issue.