Project

General

Profile

Bug #22801

Spice connection with websockets encryption

Added by Rafał Ramocki over 1 year ago. Updated 4 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Compute resources
Target version:
-
Difficulty:
Triaged:
No
Bugzilla link:
Pull request:
Team Backlog:
Fixed in Releases:
Found in Releases:

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.

History

#1 Updated by Rafał Ramocki over 1 year ago

  • Subject changed from Spice connection websockets encryption to Spice connection with websockets encryption

#3 Updated by Tomer Brisker 4 months ago

  • Category set to Compute resources

Also available in: Atom PDF