9606c80402
Starting in noVNC v1.1.0, the token query parameter is no longer
forwarded via cookie [1]. We must instead use the 'path' query
parameter to pass the token through to the websocketproxy [2].
This means that if someone deploys noVNC v1.1.0, VNC consoles will
break in nova because the code is relying on the cookie functionality
that v1.1.0 removed.
This modifies the ConsoleAuthToken.access_url property to include the
'path' query parameter as part of the returned access_url that the
client will use to call the console proxy service.
This change is backward compatible with noVNC < v1.1.0. The 'path' query
parameter is a long supported feature in noVNC.
Co-Authored-By: melanie witt <melwittt@gmail.com>
Closes-Bug: #1822676
[1]
|
||
---|---|---|
.. | ||
SCH_5007_V00_NUAC-multi_nic_OpenStack-Flat-DHCP-manager.jpg | ||
SCH_5007_V00_NUAC-multi_nic_OpenStack-Flat-manager.jpg | ||
SCH_5007_V00_NUAC-multi_nic_OpenStack-VLAN-manager.jpg | ||
SCH_5007_V00_NUAC-multi_nic_OpenStack.vsd | ||
SCH_5009_V00_NUAC-VNC_OpenStack.png | ||
SCH_5009_V00_NUAC-VNC_OpenStack.svg | ||
SCH_5009_V00_NUAC-VNC_OpenStack.vsd | ||
serial-console-flow.svg |