Bug #22801
closed
Spice connection with websockets encryption
Added by Rafał Ramocki almost 7 years ago.
Updated over 3 years ago.
Category:
Compute resources
|
Description
When websockets_encryption is set to true on foreman 1.16 spice doesn't work because JavaScript ./app/assets/javascripts/spice.js (line 5) have hardcoded schema "ws://" that in this case should be "wss://". Websockets encryption is required to have spice working on Chrome (version 64.0.3282.140) without additional configuration as it by default refuses to connect to websockets without encryption and truted certificate. File is unchanged in current head.
- Subject changed from Spice connection websockets encryption to Spice connection with websockets encryption
- Category set to Compute resources
- Status changed from New to Ready For Testing
- Assignee set to Ewoud Kohl van Wijngaarden
- Pull request https://github.com/theforeman/foreman/pull/8515 added
- Triaged changed from No to Yes
- Found in Releases 1.2.0 added
- Pull request https://github.com/theforeman/foreman/pull/8698 added
- Fixed in Releases 3.1.0 added
- Target version set to 3.0.0
Merged for 3.1.0 but I think it can be picked to 3.0.0. Setting target version so we don't forget.
- Status changed from Ready For Testing to Closed
- Pull request https://github.com/theforeman/foreman/pull/8717 added
- Fixed in Releases 3.0.0 added
- Fixed in Releases deleted (
3.1.0)
Also available in: Atom
PDF