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]
|
||
|---|---|---|
| .. | ||
| v2.6 | ||
| v2.8 | ||
| get-rdp-console-post-req.json | ||
| get-rdp-console-post-resp.json | ||
| get-serial-console-post-req.json | ||
| get-serial-console-post-resp.json | ||
| get-spice-console-post-req.json | ||
| get-spice-console-post-resp.json | ||
| get-vnc-console-post-req.json | ||
| get-vnc-console-post-resp.json | ||