lexible.
>
> After we acknowledge that CORS is a necessary feature of oVirt Engine
> (in relation to SSO/REST usage from external application context), we
> should introduce a better interface to manage CORS settings, *without*
> having to restart Engine on each change.
>
> Rega
To: "Marek Libra" , "devel"
> Sent: Monday, December 12, 2016 9:22:03 AM
> Subject: Re: [ovirt-devel] SSO/CORS for remote non-Java apps
>
> On 12/12/2016 08:03 AM, Marek Libra wrote:
> > The proposed way is:
> > - use CORS filter for eng
On 12/12/2016 08:03 AM, Marek Libra wrote:
> The proposed way is:
> - use CORS filter for enginesso.war (https://gerrit.ovirt.org/68062)
> - at host installation, add the host to CORSAllowedOrigins
>- on engine host: # engine-config -s 'CORSAllowedOrigins=[host IPs]'
>
> So if Cockpit's plugin
The proposed way is:
- use CORS filter for enginesso.war (https://gerrit.ovirt.org/68062)
- at host installation, add the host to CORSAllowedOrigins
- on engine host: # engine-config -s 'CORSAllowedOrigins=[host IPs]'
So if Cockpit's plugin accesses the oVirt REST API, CORS will work.'
On Fri,
Hi,
How can external, purely JavaScript application, running in a browser and
served from non-engine host access the oVirt REST API?
Recent SSO implementation does not provide CORS support. It can be fixed by
https://gerrit.ovirt.org/68062 .
How shall this support for external application look l
