| 2012-11-02 16:36:45 |
Gary Poster |
bug |
|
|
added bug |
| 2012-12-17 12:25:30 |
Nicola Larosa |
juju-gui: assignee |
|
Nicola Larosa (teknico) |
|
| 2012-12-18 17:49:58 |
Nicola Larosa |
juju-gui: assignee |
Nicola Larosa (teknico) |
|
|
| 2012-12-20 11:19:36 |
Nicola Larosa |
description |
You should be able to provide a certificate as an optional value. If you don't, a generated one is used. |
Pass the same certificate and private key used by nginx to the environment, and configure the websocket connection to use HTTPS and WSS, |
|
| 2012-12-20 14:10:31 |
Nicola Larosa |
juju-gui: assignee |
|
Nicola Larosa (teknico) |
|
| 2012-12-20 14:21:31 |
Nicola Larosa |
description |
Pass the same certificate and private key used by nginx to the environment, and configure the websocket connection to use HTTPS and WSS, |
Pass the same certificate and private key used by nginx to the API environment, and configure the websocket connection to use HTTPS and WSS. |
|
| 2012-12-20 14:22:32 |
Nicola Larosa |
summary |
GUI charm should require HTTPS connections to the environment by default |
Charm should require an HTTPS connection to the API environment |
|
| 2012-12-20 14:23:51 |
Nicola Larosa |
summary |
Charm should require an HTTPS connection to the API environment |
Charm should require an encrypted connection to the API environment |
|
| 2012-12-21 15:21:03 |
Nicola Larosa |
branch linked |
|
lp:~teknico/charms/precise/juju-gui/encrypt-api-env-connection |
|
| 2012-12-21 18:11:51 |
Nicola Larosa |
description |
Pass the same certificate and private key used by nginx to the API environment, and configure the websocket connection to use HTTPS and WSS. |
Pass the same certificate and private key used by nginx to the API environment, and configure the websocket connection to use WSS. |
|
| 2012-12-21 18:16:10 |
Nicola Larosa |
juju-gui: status |
Triaged |
In Progress |
|
| 2013-01-04 21:28:02 |
Gary Poster |
juju-gui: status |
In Progress |
Fix Released |
|
