Access & security
Configure gateway access, browser origins, network rules, and team permissions.
Configure API access
Gateway credentials identify an integration, while IdP tokens identify app users. Configure the layers your action requires and test them together from the client that will make real requests.
2 min readSign a gateway request
Cloudgate signature authentication uses HMAC-SHA512 over the timestamp, method, path with query, and exact request body. The client sends the API key, timestamp, and hexadecimal signature as headers.
2 min readAllow browser origins with CORS
CORS Origin controls which websites can make browser requests to your sandbox and production gateway APIs. It is configured separately from country and IP validation.
2 min readCountry, IP, and incident access controls
Use Origin Validator for network-origin restrictions and Under Attack controls when responding to suspicious traffic. Review the affected scope and verify that intended clients still have access.
2 min readTeam users, roles, and permissions
Account users administer your Cloudgate workspace. Give each person the permissions needed for their work, and manage application end users separately through the Identity Provider.
2 min read