Skip to content

Commit 526de66

Browse files
docs(kubernetes): say tenant-supplied issuer in CustomConfig mode
In CustomConfig mode the chart provisions no Keycloak objects and does not supply the issuer, the tenant does. Calling it operator-supplied was the wrong way round. Raised by gemini-code-assist on #596 and left unaddressed there. Assisted-By: Claude <[email protected]> Signed-off-by: Myasnikov Daniil <[email protected]>
1 parent ebe486e commit 526de66

2 files changed

Lines changed: 2 additions & 2 deletions

File tree

‎content/en/docs/next/kubernetes/oidc-authentication.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -97,7 +97,7 @@ spec:
9797
name: acme-byo-authn-config # Secret with a `config.yaml` key holding the AuthenticationConfiguration
9898
```
9999

100-
Setting both `config` and `secretRef.name` (or neither) fails the render. In `CustomConfig` mode no Keycloak objects are provisioned in `cozy`; the tenant apiserver trusts the operator-supplied issuer directly.
100+
Setting both `config` and `secretRef.name` (or neither) fails the render. In `CustomConfig` mode no Keycloak objects are provisioned in `cozy`; the tenant apiserver trusts the tenant-supplied issuer directly.
101101

102102
Ensure your BYO issuer emits the `email` claim in the JWT. Every conformant OIDC provider does when the client requests the `email` scope. If you distribute a hand-crafted kubeconfig instead of using the chart-generated one, remember to include `--oidc-extra-scope=email` in the `kubectl oidc-login` exec block.
103103

‎content/en/docs/v1.6/kubernetes/oidc-authentication.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -97,7 +97,7 @@ spec:
9797
name: acme-byo-authn-config # Secret with a `config.yaml` key holding the AuthenticationConfiguration
9898
```
9999

100-
Setting both `config` and `secretRef.name` (or neither) fails the render. In `CustomConfig` mode no Keycloak objects are provisioned in `cozy`; the tenant apiserver trusts the operator-supplied issuer directly.
100+
Setting both `config` and `secretRef.name` (or neither) fails the render. In `CustomConfig` mode no Keycloak objects are provisioned in `cozy`; the tenant apiserver trusts the tenant-supplied issuer directly.
101101

102102
Ensure your BYO issuer emits the `email` claim in the JWT. Every conformant OIDC provider does when the client requests the `email` scope. If you distribute a hand-crafted kubeconfig instead of using the chart-generated one, remember to include `--oidc-extra-scope=email` in the `kubectl oidc-login` exec block.
103103

0 commit comments

Comments
 (0)