https://engine.speedle.io/tags/https/ Recent content in Https on Speedle Hugo -- gohugo.io en-us https://engine.speedle.io/docs/security/ Mon, 01 Jan 0001 00:00:00 +0000 https://engine.speedle.io/docs/security/ Protect both API transports Speedle’s standalone PMS and ADS expose REST and gRPC. Both now use the same --insecure, --cert, --key, --client-cert and --force-client-cert transport settings. Invalid certificates or trust configuration cause startup to fail; secure mode does not fall back to plaintext. TLS encrypts the connection and authenticates the server. To require authenticated clients, provide a client CA with --client-cert and set --force-client-cert=true. Without that flag, a configured CA validates a client certificate only when the client supplies one.