Thanks alaski for the quick guidance!
In order to not force a new requirement, we can try to load that configuration and use it when possible... Then we can amend the OSSA with a note saying that the websocketproxy server needs access to nova.conf in order to have full protection...
And just to be sure, xvpvncproxy_base_url and html5proxy_base_url are out of scope here right ?
Thanks alaski for the quick guidance!
In order to not force a new requirement, we can try to load that configuration and use it when possible... Then we can amend the OSSA with a note saying that the websocketproxy server needs access to nova.conf in order to have full protection...
And just to be sure, xvpvncproxy_ base_url and html5proxy_base_url are out of scope here right ?