The General module centralizes the global parameters that AI Gateway uses to validate access tokens and integrate with Sensedia Platform. Unlike the other features, General is not a listing page. It is a single page with an update form.
IMPORTANTThe values registered here affect all gateway routes. Changing the Authorization Server changes who issues the tokens the gateway accepts: tokens issued by the previous provider start being rejected as soon as the new configuration is saved.
Learn how to:
In the side menu, access General. The form opens directly on the page. There is no listing or modal.
Decide which Authorization Server the gateway should use to validate tokens: the platform default or your own OpenID provider.
Fill in or update the remaining fields (see Form fields).
With the Use a custom authorization server option unchecked, the gateway validates access tokens against the platform's own Authorization Server. This is the default mode and requires no additional configuration: the credentials issued in AI Agents and the scopes registered in Scopes work without you providing any URL.
Check Use a custom authorization server to validate tokens against your own OpenID Provider. When you check the option, the Well-Known URL field appears and becomes required.
Provide the URL of your provider's OpenID discovery document (usually ending in /.well-known/openid-configuration). On save, the gateway:
issuer) and the address of the public key set (jwks_uri) from it.Only after these three checks is the configuration accepted. From then on, the gateway accepts only tokens issued by the discovered issuer and signed by one of those keys.
THE URL MUST BE PUBLICThe Well-Known URL is accessed by the gateway itself at the moment you save, so it must be a publicly reachable address. Internal, private, or loopback URLs are rejected.
VALIDATION ERRORSIf any of the three steps fails — unreachable document, missing
jwks_uri, or an empty key set or one without a signing key — the form displays the corresponding message and the configuration is not saved. Check the URL and your provider's public availability before trying again.
To go back to the platform Authorization Server, uncheck the option — the Well-Known URL field is cleared — and click Save.
The table below covers all fields visible in the form.
Field | Type | Required | Rules |
|---|---|---|---|
| Use a custom authorization server | Checkbox | No | Unchecked, the gateway uses the platform Authorization Server. Checked, it displays the Well-Known URL field so you can connect your own OpenID Provider. |
| Well-Known URL | Text (URL) | Yes — when Use a custom authorization server is checked | URL of the provider's OpenID discovery document (e.g., https://your-idp/.well-known/openid-configuration). It must be a valid, publicly accessible URL, and the provider must expose at least one signing key. |
| Sensedia Platform Client ID | Text (sensitive, password) | No | Client ID used to authenticate with Sensedia Platform APIs. Displayed as a password field. |
| Sensedia Platform Client Secret | Text (sensitive, password) | No | Client Secret corresponding to the Sensedia Platform Client ID. Displayed as a password field. |
We use cookies to enhance your experience on our site. By continuing to browse, you agree to our use of cookies.Learn more