Project

General

Profile

Actions

Bug #9603

closed

Setting called websockets_encrypt does not work correctly

Added by Lukas Zapletal about 9 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Normal
Category:
Compute resources
Target version:
Difficulty:
trivial
Triaged:
Fixed in Releases:
Found in Releases:

Description

When you set websockets_encrypt to false (via settings or even installer) and leave the websockets_ssl_cert/key settings as is (they default to puppet cert/key), console will not work. The flag not to encrypt the communication will be passed to the HTML5 component correctly, but the websockify program will be always spawned with certificates, therefore dropping non-secured connection.


Related issues 4 (0 open4 closed)

Related to Foreman - Bug #11120: MigrateWebsocketsSetting fails with ReadOnlyRecord when websockets_encrypt is in settings.yamlClosedDominic Cleal07/15/2015Actions
Related to Foreman - Bug #11121: websockets_encrypt validation fails with settings.yaml on empty DBClosedDominic Cleal07/15/2015Actions
Has duplicate Foreman - Bug #10332: encrypt_websockets = off is not workingDuplicate04/30/2015Actions
Has duplicate Foreman - Bug #7557: websockets_encrypt setting is meaninglessDuplicate09/20/2014Actions
Actions #1

Updated by Dominic Cleal about 9 years ago

  • Category changed from Web Interface to Compute resources
Actions #2

Updated by Lukas Zapletal about 9 years ago

  • Subject changed from Websocketify spawner does not honor websockets_encrypt setting to Setting called websockets_encrypt does not work correctly

It's more complex, filed a patch already. Initially I set the Category to CR, but it did not seem like a good fit. Console could be better (as it can be bug in websocketify). Anyway, thanks :-)

Actions #3

Updated by Dominic Cleal about 9 years ago

That's OK, I usually use the CR category for console related things. Web Interface gets over-used :)

Actions #4

Updated by Daniel Lobato Garcia almost 9 years ago

  • Has duplicate Bug #10332: encrypt_websockets = off is not working added
Actions #5

Updated by Dominic Cleal almost 9 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/foreman/pull/2219 added
  • Pull request deleted ()
Actions #6

Updated by Dominic Cleal over 8 years ago

  • translation missing: en.field_release set to 63
Actions #7

Updated by Lukas Zapletal over 8 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100
Actions #8

Updated by Dominic Cleal over 8 years ago

  • Related to Bug #11120: MigrateWebsocketsSetting fails with ReadOnlyRecord when websockets_encrypt is in settings.yaml added
Actions #9

Updated by Dominic Cleal over 8 years ago

  • Related to Bug #11121: websockets_encrypt validation fails with settings.yaml on empty DB added
Actions #10

Updated by Stephen Benjamin over 8 years ago

  • Has duplicate Bug #7557: websockets_encrypt setting is meaningless added
Actions

Also available in: Atom PDF