Connection & auth

These settings describe how the protected client talks to your stack: transport flavor, optional custom protocol id, sensible concurrency limits, and where authentication should be validated.

Port

• Sets the network port the client uses when connecting to your game or gateway (when applicable).
• Must align with what your server stack actually listens on (firewalls, Docker publishes, TLS terminators).

Protocol & custom protocol

• Protocol selects the baseline wire / handshake family your integration expects.
• Custom protocol (premium-gated when exposed to clients) allows a numeric discriminator for engines that multiplex multiple protocol handlers — keep it stable across client and server builds.

Max clients

• Caps concurrent client connections from the perspective of the protection bundle where this limit is enforced (exact semantics follow your integration).
• Tune for your shard capacity; raising without server headroom can cause overload rather than protection issues.

Auth host

• The hostname or endpoint your client should use for authentication / session handshakes with your backend — not Sunrise infrastructure.
• Use a hostname your TLS certificates and DNS actually resolve for every environment (dev/stage/prod).

Validation checklist

• Port open on firewalls and matches server bind.
• Protocol ids consistent between client build and server.
• Auth host reachable from player networks (no internal-only DNS in production).

Related: Client interface, Installation.