Bug #34146 subscription key can get out of sync with enterprise website
Submitted: 29 Jan 2008 19:38 Modified: 4 Feb 2008 20:10
Reporter: Sloan Childers Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Enterprise Monitor: Web Severity:S3 (Non-critical)
Version:1.3 OS:Any
Assigned to: Joshua Ganderson CPU Architecture:Any

[29 Jan 2008 19:38] Sloan Childers
Description:
Currenty MEM does not pull a new subscription key from the enterprise website unless the customer changes their enterprise credentials in the settings page.  This means that the product will whine about an expired license inappropriately.

How to repeat:
Manually install a different license than your enterprise credentials would normally correlate to.

Suggested fix:
▼    Subscription expired and never updated - For 1.3:
    ▼    1. manual check: add key check on "check for updates"
    •    note: will also help if they have upgraded/downgraded
    ▼    2. add text to product info / subscription expired warning
    •    if you've renewed your subscription, click _here_ to update your product info (same action as "check for updates")
    •    3. Change Enterprise portal to Enterprise website (text only change)
    ▼    later
    ▼    add "Enable online updates" checkbox
    •    default checked
    •    if checked, once per day or every login we validate subscription asynchronously.
    •    consider not always updating key (unless it needs it)
[29 Jan 2008 19:43] Sloan Childers
r8858 development-1.2.1 adds the subscription key update as part of an online advisor bundle update
[30 Jan 2008 18:57] Joshua Ganderson
r8867 - Adding new update key action, access to it through conditional section on product info page, and some minor fixes to properties file. Translations for new messages not yet complete.
[31 Jan 2008 5:15] Sloan Childers
r8886 development-1.2.1
[1 Feb 2008 23:19] Bill Weber
verified that either updating advisors or clicking the update button on the Product Information page will update the subscription key in build 1.3.0.8876
[4 Feb 2008 20:10] Peter Lavin
Thank you for your bug report. This issue has been addressed in the documentation. The updated documentation will appear on our website shortly, and will be included in the next release of the relevant products.

Added to the changelog for version 1.2/1.3. Also added related information to the body of the documentation.