Bug #9603
closed
Setting called websockets_encrypt does not work correctly
Added by Lukas Zapletal about 9 years ago.
Updated almost 6 years ago.
Category:
Compute resources
|
|
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.
- Category changed from Web Interface to Compute resources
- 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 :-)
That's OK, I usually use the CR category for console related things. Web Interface gets over-used :)
- Has duplicate Bug #10332: encrypt_websockets = off is not working added
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/2219 added
- Pull request deleted (
- translation missing: en.field_release set to 63
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
- Related to Bug #11120: MigrateWebsocketsSetting fails with ReadOnlyRecord when websockets_encrypt is in settings.yaml added
- Related to Bug #11121: websockets_encrypt validation fails with settings.yaml on empty DB added
- Has duplicate Bug #7557: websockets_encrypt setting is meaningless added
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by