If this authentication attempt is successful, then one or more secondary connections are made from the Horizon client. Secondary Horizon ProtocolsĪfter the Horizon Client has established secure communication to one of the UAGs or CSes, the user authenticates. This has the effect of evenly distributing the traffic from different clients across the available set of UAGs or CSes. The load balancer will usually select the appliance based first on availability, and then out of the available appliances will route traffic based on the different load-balancing algorithm. In a load balanced environment as shown above in Figure 1, the load balancer will route this connection to one of the UAGs or CSs. This protocol is sometimes known as the Horizon XML-API control protocol. It uses XML structured messages over HTTPS (HTTP over SSL). This is a control protocol for authentication, authorization and session management. The user enters a hostname at the Horizon Client and this starts the primary Horizon protocol. Following successful authentication, one or more secondary protocols are also made. The first connection is always the primary XML-API protocol over HTTPS. ![]() ![]() When a Horizon Client user connects to a Horizon environment, several different protocols are used. Horizon Protocols | FortiADC Private Cloud 6.1.0
0 Comments
Leave a Reply. |