----- Original Message -----
From: "Neil Schulz" <neil.schulz(a)neteasy.us>
To: "Alon Bar-Lev" <alonbl(a)redhat.com>, users(a)ovirt.org
Sent: Monday, January 13, 2014 7:50:06 PM
Subject: Re: [Users] noVNC https certs
So, this is the only way to stop having to accept the cert?
I'd have to tell all our clients to download and install that cert to
their workstation?
Yes, the other option is to buy certificates from already trusted 3rd parties, and install
it for both apache and websocket proxy instead the internally issued ons.
On 1/13/2014 12:48 PM, Alon Bar-Lev wrote:
> You should trust the engine internal CA.
>
> it can be downloaded from
http://engine/ca.crt, mark it as trusted for web
> identity.
>
> ----- Original Message -----
>> From: "Neil Schulz" <neil.schulz(a)neteasy.us>
>> To: users(a)ovirt.org
>> Sent: Monday, January 13, 2014 7:44:35 PM
>> Subject: [Users] noVNC https certs
>>
>> Hey everyone,
>>
>> So far I am impressed with the product and am enjoying it thoroughly. I
>> am looking to put in new certs for noVNC, so I or clients do not have to
>> repeatedly accept the cert at https://<FQDN>:6100
>>
>> Is there a way, or documentation? I was unable to find any and the
>> default certs install on the system, I am unfamiliar with. Is there an
>> easy way of updating/replacing them for a trusted connection?
>>
>> Thank you,
>> Neil
>>
>> _______________________________________________
>> Users mailing list
>> Users(a)ovirt.org
>>
http://lists.ovirt.org/mailman/listinfo/users
>>