shc auth create-oidc-client
shc auth create-oidc-client
Section titled “shc auth create-oidc-client”create a standalone tenant OIDC client
Synopsis
Section titled “Synopsis”create a standalone tenant OIDC client. Requires an explicit --tenant and platform:manage. Platform clients and clients owned by deployments are refused. An existing client must be imported. The initial client-secret is shown once; --fields secret -o text prints that value alone.
shc auth create-oidc-client <client-id> [flags]Options
Section titled “Options” --authentication string client-secret or client-jwt (default "client-secret") -h, --help help for create-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 clearOptions inherited from parent commands
Section titled “Options inherited from parent commands” --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)SEE ALSO
Section titled “SEE ALSO”- shc auth - authenticate the CLI against a cluster
shc@docs:~$