The TLS 1.2 security protocol is enabled. Turn on this toggle to enable TLS 1.1 security protocol. Turn on this toggle to enable TLS 1.0 security protocol.

See Using PowerShell to Deploy the Unified Access Gateway Appliance. This option can be configured during PowerShell deployment by adding the tlsSignatureSchemes parameter in the ini file. Ongoing Unified Access Gateway sessions are not retained during the restart. Any changes to this option results in Unified Access Gateway services getting restarted. Else, the TLS Signature Schemes option is disabled. To configure this option, ensure that the SSL Provider option is set to JDK. For example: some of the supported signature schemes are as follows: rsa_pkcs1_sha, rsa_pkcs1_sha256, rsa_pkcs1_sha384, rsa_pss_rsae_sha256, and rsa_pss_rsae_sha384. This option allows comma-separated values. See Using PowerShell to Deploy the Unified Access Gateway Appliance.Īllows the administrator to configure the supported TLS signature algorithms used for key validation during SSL handshake. This option can be configured during PowerShell deployment by adding the tlsNamedGroups parameter in the ini file. Else, the TLS Named Groups option is disabled. Some of the supported named groups are as follows: secp256r1, secp384r1, secp521r1.

See Using PowerShell to Deploy the Unified Access Gateway Appliance.Īllows the administrator to configure the desired named groups (elliptic curves) from a list of supported named groups used for key exchange during SSL handshake. This option can be configured during PowerShell deployment by adding the sslProvider parameter in the ini file. However, CRL-based certificate revocation check is supported.Īny changes to this option results in Unified Access Gateway services getting restarted. JDK, OCSP-based certificate revocation check is not supported.

Vmware horizon client http error 503