Documentation Index
Fetch the complete documentation index at: https://docs.poolside.ai/llms.txt
Use this file to discover all available pages before exploring further.
Overview
Use this guide to update the OIDC configuration of an existing Poolside deployment. Common reasons to reconfigure include:- The OIDC client secret expired, or your identity provider rotated it.
- The Poolside deployment hostname changed, so the redirect URL no longer matches the identity provider configuration.
- The OIDC issuer URL or client ID changed.
reconfigure-tenant command to update one OIDC field or several fields in a single reconfiguration. When you update the client secret, Poolside re-encrypts it at rest.
This guide does not cover initial OIDC configuration. For the initial OIDC application setup in your identity provider, see OIDC authentication.
Prerequisites
kubectlaccess to the cluster running Poolside, with permission to exec into pods in thepoolsidenamespace.- The new OIDC values you want to apply: issuer URL, client ID, client secret, or redirect URL.
Steps
-
The
reconfigure-tenantcommand requires the tenant ID as a positional argument. Find the tenant ID from the auth API or directly from Postgres.- Auth API
- Postgres
-
If the Poolside deployment is reachable from your workstation, query the
tenant-login-optionsendpoint with any valid Poolside user email. URL-encode the@as%40.Example output: -
Copy the
uuidvalue to use it as<tenant-id>.
-
Exec into a
core-apipod and run thereconfigure-tenantcommand with the flags you want to change. Include at least one OIDC flag. Thereconfigure-tenantcommand supports the following flags:--oidc-client-id: OIDC client ID.--oidc-client-secret: OIDC client secret. Poolside encrypts this value at rest.--oidc-issuer: OIDC issuer URL.--oidc-redirect-url: OIDC redirect URL.
To rotate the client secret only:Command syntaxTo update multiple fields in one command:Example: Rotate the client secretOn success, the command prints:Example: Update multiple OIDC fields -
Verify the change.
Sign in to Poolside at
https://<your-poolside-hostname>and complete the OIDC flow. A successful sign-in confirms the new configuration is in effect. If sign-in fails, checkcore-apilogs for the OIDC error returned by the identity provider: