Test OpenBao OIDC and JWT with Authentik¶
Use this disposable kind lab to test Authentik identities against OpenBao configuration managed by this operator. It creates its own Authentik instance; no hosted account or credentials are required.
The lab installs the official Authentik Helm chart with a pinned server image and a separate
PostgreSQL instance. Review or adapt the non-secret chart settings in
hack/lab/authentik/values.yaml.
The runner passes that file to Helm; passwords and bootstrap credentials remain runtime-generated
Kubernetes Secrets, referenced by the values file. Both the database and identities are disposable. This is a test deployment,
not a production Authentik installation.
Before you start¶
Install the local lab prerequisites, including Docker, kind, Helm, kubectl and the browser runner dependencies. Run the commands from the repository root. Allow additional memory for Authentik's server, worker and PostgreSQL alongside OpenBao and the operator.
The identity provider uses HTTP only inside this disposable kind network. OpenBao connections continue to use the lab's TLS certificate and CA verification. The browser reaches Authentik through a loopback port-forward while preserving its cluster issuer URL.
Run the regression¶
Create a dedicated cluster and bootstrap the operator's OpenBao connection:
export KIND_CLUSTER=obco-authentik
export LAB_CONTEXT=kind-obco-authentik
hack/lab/up.sh raft
make lab-authentik
Provisioning generates independent passwords, a bootstrap token, an OIDC client secret and service
account credentials. It stores them in Kubernetes Secrets in obco-lab-authentik; they are never
printed or committed. The provisioning command refuses an existing Authentik namespace instead of
silently replacing identities. To repeat the regression on an existing lab:
The run covers nine identities, admin, read and ops in root, alpha and beta. The
tenant namespaces are saas-authentik-alpha and saas-authentik-beta. What those identities are
allowed to do is in the OIDC permissions showcase.
Troubleshoot a failure¶
Inspect readiness without exposing Secret contents:
kubectl --context "$LAB_CONTEXT" -n obco-lab-authentik get pods
kubectl --context "$LAB_CONTEXT" -n obco-lab get jwtauthroles,jwtauthconfigs
If installation fails, check image pulls and available memory. If a CRD is not Ready, inspect its conditions and references. For login failures, use the test's safe phase/category diagnostics; do not publish raw provider logs, callback URLs, tokens or Kubernetes Secrets.
An interrupted provisioning run may leave a partial disposable instance. Delete the dedicated cluster and start again rather than adopting or overwriting those resources.
Clean up¶
Deleting the lab removes the generated credentials and ephemeral PostgreSQL data. No external Authentik tenant is modified.
Next steps¶
- OIDC permissions showcase explains the access journeys.
- JWT and OIDC authentication covers operator configuration.
- Authentik documents automated bootstrap, OAuth2/OIDC providers, and native machine authentication.