MySQL Bugs: #31507: Allow the dashboard to use a proxy to communicate for license key and advisors

Bug #31507	Allow the dashboard to use a proxy to communicate for license key and advisors
Submitted:	10 Oct 2007 15:08	Modified:	21 Jul 2009 15:04
Reporter:	Harrison Fisk	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Enterprise Monitor: Server	Severity:	S3 (Non-critical)
Version:	1.2, 2.0.1.7125	OS:	Any
Assigned to:	Sloan Childers	CPU Architecture:	Any

Description:
The MySQL Enterprise Manager dashboard can communicate with https://enterprise.mysql.com using your username and password to download the license key and advisor bundle, however it can not make use of a proxy to do so.  Many corporate firewalls require the use of a proxy for all HTTP and HTTPS traffic.  

This requires the work around of always having to manually download license keys and advisor bundles by hand.

How to repeat:
Try to run the setup using a username/password authentication from behind a firewall which requires a proxy.

Suggested fix:
Allow the ability to store proxy information to use.

Phase 1 has been pushed to bzr+ssh://schilders@64.212.38.67/bzrroot/etools/trunk
- it uses server properties to configure proxy
INSERT INTO map_entries VALUES (1,'<proxy ip address>','http.proxyHost');
INSERT INTO map_entries VALUES (1,'<proxy port>','http.proxyPort');
- if the proxy requires authentication
INSERT INTO map_entries VALUES (1,'<proxy user name>','http.proxyUser');
INSERT INTO map_entries VALUES (1,'<proxy password>','http.proxyPassword');

Phase 2 will add a user interface...

Passing the torch for proxy UI implementation.

(trunk:)
revno: 6643
revision-id: jsled@asynchronous.org-20090129184241-rvt3johxxut7gfz6
parent: jsled@asynchronous.org-20090129174802-ersak067isjevxr6
committer: Josh Sled <jsled@asynchronous.org>
branch nick: local
timestamp: Thu 2009-01-29 13:42:41 -0500
message:
  Bug#31507: Add UI support for setting up an HTTP Proxy during first-time setup, and in global settings; add jquery for UI support, here.

I'm leaving this open and assigning back to Sloan for a bit more testing before closing (thanks, Sloan! :)

trunk is ready for testing the new UI

verified this has been added to the UI - waiting for customer verification of fix

Let's get this one documented for the upcoming release.  The customer support issue has been closed.

An entry was added to the 2.1.0 changelog:

The Enterprise Dashboard could communicate with https://enterprise.mysql.com using the customer username and password to download the license key and advisor bundle. However, it could not make use of a proxy to do so. This was a problem as many corporate firewalls required the use of a proxy for all HTTP and HTTPS traffic.

The work around of having to manually download license keys and advisor bundles by hand was inconvenient.