Bug #39198 Dashboard does not support https
Submitted: 2 Sep 2008 19:18 Modified: 14 Oct 2008 16:10
Reporter: Diego Medina Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Enterprise Monitor: Installing Severity:S2 (Serious)
Version:2.0.0.7042 OS:Any
Assigned to: MC Brown CPU Architecture:Any

[2 Sep 2008 19:18] Diego Medina
Description:
You cannot use https to connect to the dashboard.

When accessing this url
https://127.0.0.1:18080/

you get this error "The connection was interrupted"

How to repeat:
1- Install the monitor and start it
2- Go to https://127.0.0.1:18080/

and you will see the error

notes:

Using wget you get:

--2008-09-02 15:13:18--  https://127.0.0.1:18080/
Connecting to 127.0.0.1:18080... connected.
Unable to establish SSL connection.
[2 Sep 2008 19:32] Diego Medina
Using https://127.0.0.1:18443/   (note different port number) does not fix the problem. The page just takes longer to load.

Same as 

http://127.0.0.1:18443/ (no https) (just in case)
[3 Sep 2008 3:06] Mark Matthews
Hi. Can we get the tomcat in our stack to have SSL support out of the box? We won't configure the webapp to require redirection at this point in time, because our agents don't yet work with SSL, however we'd like customers to have the option to use SSL.

This will require us to ship with a self-signed cert, along with a keystore that is pointed to in server.xml. If you need more information from us on the self-signed certificate contents, or anything else, contact Andy.

I've tested this using the tomcat-6.0 "ssl" documentation instructions, and once a self-signed cert is installed in a keystore, and the SSL connector is uncommented, it works as expected.

Thanks!
  -Mark
[10 Sep 2008 17:36] BitRock Merlin
Patch sent to Keith.
[19 Sep 2008 18:00] Keith Russell
Patch applied in versions => 2.0.0.7055.
[29 Sep 2008 21:35] Diego Medina
Verified fixed on 2.0.0.7061
[14 Oct 2008 16:10] Tony Bedford
An entry was added to the 2.0 changelog:

It was not possible to establish a connection with the Dashboard using the SSL protocol (https://).