Skip to content
SHC Docs

shc auth update-oidc-client

replace a standalone tenant OIDC client’s configuration

replace a standalone tenant OIDC client’s configuration. Requires an explicit --tenant and platform:manage. Platform clients and clients owned by deployments are refused. Supply --redirect-uri, --web-origin and --authentication on every update. Use --web-origin= to clear allowed origins. Authentication is fixed at create and must match the live client. To change it, delete and create the client, or import the new one.

shc auth update-oidc-client <client-id> [flags]
--authentication string client-secret or client-jwt
-h, --help help for update-oidc-client
--jwks-url string absolute HTTPS JWKS URL required for client-jwt
--redirect-uri stringArray allowed redirect URI; repeat for multiple values (required)
--signing-alg string JWT signing algorithm required for client-jwt
-t, --tenant string tenant realm that holds the client (required)
--web-origin stringArray allowed web origin; repeat for multiple values, or use --web-origin= to clear
--config stringArray extra YAML config file to layer on top of auto-discovered config; repeatable, later files win
-d, --debug enable debug mode (default: $SHC_DEBUG)
-e, --environment string environment name (default: "prod", or "default" on an estate with no licence and no trial; $SHC_ENVIRONMENT and shc ctx -e override it, and the "master" tenant is always "default")
--exclude string comma-separated dotted paths to drop
--fields string comma-separated columns/keys to show (and their order)
--filter string comma-separated dotted paths to keep (drops everything else)
-o, --output string output format: tty|text|json|yaml (default: $SHC_OUTPUT)
-s, --stack string stack name (default: $SHC_STACK)
-v, --verbose verbose output (default: $SHC_VERBOSE)
  • shc auth - authenticate the CLI against a cluster