HTTPS Protocol
- Last UpdatedJan 13, 2026
- 1 minute read
The HTTPS protocol uses HTTP binding (basic or WSHttp) and transport security. It relies on certificates for client authentication. By default, transport security authenticates the service with a service certificate and the client with a client certificate.
When two locations communicate, such as a hub and a satellite, their roles alternate. When the hub sends a request and the satellite responds, the hub acts as the client (sending) and the satellite acts as the service (listening). The roles reverse when the satellite sends data back.
To run Global over HTTPS, each location requires two certificates: a service certificate for when the location daemon acts as a service (listening) and a client certificate for when the location acts as a client (sending).