Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions content/docs/latest/nebraska/authorization.md
Original file line number Diff line number Diff line change
Expand Up @@ -51,6 +51,10 @@ because the defaults are set at half.

- In the browser, access `http://localhost:8000`

## Custom CA Certificates

If your OIDC provider or update server uses a certificate signed by a non-public CA (e.g., internal CA or Let's Encrypt staging), pass `--ca-file=/path/to/ca-bundle.pem` to trust it. The custom CAs are added to the system trust store — existing system CAs remain trusted. This applies to both the OIDC client and the syncer. In Helm deployments, set `config.caFile` instead.

# Deploying Nebraska with OIDC authentication mode

> **⚠️ OIDC Implementation Updated ⚠️**
Expand Down Expand Up @@ -482,6 +486,9 @@ $ helm install my-nebraska nebraska/nebraska --values nebraska-values.yaml
- SSO session will handle re-authentication transparently if still valid.
- Go to your providers token settings (either under realm or specific client) and increase the access token lifespan from minutes to hours.

- **"x509: certificate signed by unknown authority"**
- Use `--ca-file` to trust your OIDC provider's or update server's CA certificate.

- **Auth0: "JWT malformed" or decode errors**
- Ensure Implicit grant is disabled in application settings.
- Verify audience parameter is set correctly.
Expand Down
Loading