Construction of websocket URL is incorrect if SSL is enabled on Undercloud
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
High
|
Honza Pokorny |
Bug Description
When SSL is enabled on the Undercloud, logic handling the encrypted Zaqar websocket URL generates an unusable uri. The URI becomes wss:// to indicate a secure websocket connection, but there is no way to change the port number. Instead, the UI defaults to using a URI of wss://<undercloud host>:<port UI is running on>.
This was discovered by running the UI on a virtual host that Apahce is proxying with mod_proxy. In this case, mod_proxy is proxying port 3005 to the UI's gulp server, which listens on port 3000. In this case, the websocket URL should not be wss://<undercloud host>:3500, but in fact, wss://<undercloud host>:9000.
In addition, under these same conditions, the zaqar_websocket_url value as defined in dist/js/
Changed in tripleo: | |
importance: | Undecided → High |
status: | New → Triaged |
Changed in tripleo: | |
assignee: | nobody → Honza Pokorny (hpokorny) |
Currently the GUI uses zaqar websocket url from tripleo_ ui_config. js and if it is not specified there it defaults to ws://${ location. hostname} :9000 so it should never try to connect to GUI app port.
GUI needs to update it's code to use websocket url from keystone auth response since that url is now available in endpoints list.