2b8d5a0b88
To secure communications from the proxy server to the compute nodes using VeNCrypt authentication scheme. In a previous patch a TLS server certificate was deployed to compute nodes, this patch makes use of this same server cert for securing VNC sessions on compute nodes. It is recommended that this certificate be issued by a dedicated certificate authority solely for the VNC service, as libvirt does not currently have a mechanism to restrict what certificates can be presented by the proxy server. This has not been implemented to reduce complexity. In addition the noVNC proxy needs to present a client certificate so only approved VNC proxy servers can connect to the Compute nodes. The PKI role has been used to create a client certificate for the nova console nodes. Related Nova docs: https://docs.openstack.org/nova/latest/admin/remote-console-access.html To help with the transition from from unencrypted VNC to VeNCrypt, initially compute nodes auth scheme allows for both encrypted and unencrypted sessions using the variable `nova_vencrypt_auth_scheme`, this will be removed in future releases. Change-Id: Iafb788f80fd401c6ce6e4576bafd06c92431bd65
17 lines
678 B
YAML
17 lines
678 B
YAML
---
|
|
features:
|
|
- |
|
|
Enable VeNCrypt authentication scheme from noVNC proxy to compute nodes.
|
|
When using HTTPS, the TLS encryption only applies to data between the
|
|
tenant user and proxy server. To provide protection from the noVNC proxy
|
|
to the Compute Nodes, it is necessary to enable the VeNCrypt
|
|
authentication scheme for VNC.
|
|
|
|
A pre-existing PKI (Public Key Infrastructure) setup is
|
|
required.
|
|
|
|
Initially to help with the transition from unencrypted VNC to
|
|
VeNCrypt, compute nodes auth scheme allows for both encrypted and
|
|
unencrypted sessions using the variable `nova_vencrypt_auth_scheme`,
|
|
this will be removed in future releases.
|