topic Self-signed SSL certificate / View 5 in Horizon Desktops and Apps

Self-signed SSL certificate / View 5

don1304 — Wed, 02 May 2012 21:40:19 GMT

Self-signed SSL certificate / View 5

Can we setup Self-signed SSL certificate with View 5? As I get error message after upgrading the View environment from 4.6 to 5.0 for both Internal and external conenctions .

Error Message :

Vmware View Canot verify the identity of the server you have contacted . Your credentials will not be secure .Contact your administrator to ask if this server can be trusted.

Just FYI , we dont have a CA server or any thridparty SSL certifcate .

Re: Self-signed SSL certificate / View 5

eeg3 — Wed, 02 May 2012 21:52:36 GMT

You should be able to change this as detailed below:

View clients now follow the well-known browser model for handling certificates, displaying errors detected in the certificate presented by View Connection Server, or in the certificate trust chain. Administrators can set the Certificate verification mode group policy to enforce strict certificate checking; if any certificate error occurs, the user cannot connect to View Connection Server. Alternatively, administrators can use the default Warn But Allow mode, which supports self-signed server certificates and lets users connect to View Connection Server with certificates that have expired or are not yet valid. If necessary, administrators can also set a No Security mode that lets users connect without certificate checking.

More details here: http://vinfrastructure.it/en/2011/12/vmware-view-5-certificate-warning/

Re: Self-signed SSL certificate / View 5

don1304 — Wed, 02 May 2012 22:17:51 GMT

Thanks ....But doing this step , it still displays the https MARKED in red on the View Client .

Attached the screenshot , We never had this issue in 4.6 .

Re: Self-signed SSL certificate / View 5

eeg3 — Wed, 02 May 2012 22:19:09 GMT

I believe that is an intended feature of View 5. Perhaps someone else can confirm.

Re: Self-signed SSL certificate / View 5

Linjo — Thu, 03 May 2012 11:08:29 GMT

This would be the expected behavious if the certificate is not trusted by the client.

Its very similar to any webserver having self-signed certificate.

To solve this import the root-certificate on the client or use a certificate in a chain already trusted by the client.

// Linjo