Project

General

Profile

Bug #9603

Setting called websockets_encrypt does not work correctly

Added by Lukas Zapletal over 4 years ago. Updated about 1 year ago.

Status:
Closed
Priority:
Normal
Category:
Compute resources
Target version:
Difficulty:
trivial
Triaged:
Bugzilla link:
Team Backlog:
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

Related to Foreman - Bug #11120: MigrateWebsocketsSetting fails with ReadOnlyRecord when websockets_encrypt is in settings.yamlClosed2015-07-15
Related to Foreman - Bug #11121: websockets_encrypt validation fails with settings.yaml on empty DBClosed2015-07-15
Has duplicate Foreman - Bug #10332: encrypt_websockets = off is not workingDuplicate2015-04-30
Has duplicate Foreman - Bug #7557: websockets_encrypt setting is meaninglessDuplicate2014-09-20

Associated revisions

Revision 97c34475 (diff)
Added by Lukas Zapletal about 4 years ago

Fixes #9603 - fixed websockets_* set of settings

History

#1 Updated by Dominic Cleal over 4 years ago

  • Category changed from Web Interface to Compute resources

#2 Updated by Lukas Zapletal over 4 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 :-)

#3 Updated by Dominic Cleal over 4 years ago

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

#4 Updated by Daniel Lobato Garcia over 4 years ago

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

#5 Updated by Dominic Cleal about 4 years ago

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

#6 Updated by Dominic Cleal about 4 years ago

  • Legacy Backlogs Release (now unused) set to 63

#7 Updated by Lukas Zapletal about 4 years ago

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

#8 Updated by Dominic Cleal about 4 years ago

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

#9 Updated by Dominic Cleal about 4 years ago

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

#10 Updated by Stephen Benjamin almost 4 years ago

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

Also available in: Atom PDF