Table of Contents
Advertisement
Encrypting Pre-Session Communications with PCoIP
Connection Managers
Before a PCoIP session is negotiated with a PCoIP host using a PCoIP Connection Manager, each
user is authenticated and then selects a desktop from a list of authorized resources. To complete
this authentication process, the Tera2 PCoIP Zero Client communicates with a PCoIP Connection
Manager over port 443 using one of the following cipher suites:
• TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
• TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
• TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
• TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
• TLS_RSA_WITH_AES_256_GCM_SHA384
• TLS_RSA_WITH_AES_128_GCM_SHA256
• TLS_RSA_WITH_AES_256_CBC_SHA256
• TLS_RSA_WITH_AES_128_CBC_SHA256
• TLS_RSA_WITH_AES_256_CBC_SHA
• TLS_RSA_WITH_AES_128_CBC_SHA
System Configuration Requirements
These cipher suites can only be configured at the host, and have a minimum requirement of TLS 1.1.
Encrypting PCoIP Session Negotiation with PCoIP Hosts
After user authentication and resource selection, PCoIP sessions are negotiated between the
Tera2 PCoIP Zero Client and the PCoIP host. These negotiations take place before the PCoIP
session is established, and are secured using these Max Compatibility and Suite B cipher suites:
• TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
• TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
• TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
© 2020 Teradici
Encrypting Pre-Session Communications with PCoIP Connection Managers
403
Advertisement
Table of Contents
