public/geek-cookbook
1
0
Fork 0
mirror of https://github.com/funkypenguin/geek-cookbook/ synced 2025-12-14 02:06:32 +00:00
Code Issues Releases Wiki Activity

Update casing for Keycloak

Browse Source 
Signed-off-by: David Young <davidy@funkypenguin.co.nz>
This commit is contained in:
David Young
2023-11-15 15:26:39 +13:00
parent 94da6c77dc
commit af8eae4cfd
8 changed files with 17 additions and 17 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
docs/kubernetes/oidc-authentication/index.md
View File

@@ -19,12 +19,12 @@ True to form, Kubernetes doesn't provide any turnkey access solution, but all th
## Requirements
Securing access to Kubernetes' API server requires an OIDC provider, be it an external service like Auth0 or Octa, or a self-hosted, open-source IDP like KeyCloak or [authentik][k8s/authentik].
Securing access to Kubernetes' API server requires an OIDC provider, be it an external service like Auth0 or Octa, or a self-hosted, open-source IDP like Keycloak or [authentik][k8s/authentik].
### Setup Provider
1. Setup [Authentik for Kubernetes API authentication](/kubernetes/authentication/authentik/)
2. KeyCloak (*coming soon*)
2. Keycloak (*coming soon*)
### Configure Kubernetes for OIDC auth

4
docs/kubernetes/oidc-authentication/keycloak.md
View File

@@ -4,7 +4,7 @@ description: How to configure your Kubernetes cluster for OIDC authentication wi
---
# Authenticate to Kubernetes with OIDC on K3s
This recipe describes how to configure K3s for OIDC authentication against a [keycloak][k8s/keycloak] instance.
This recipe describes how to configure K3s for OIDC authentication against a [Keycloak][k8s/keycloak] instance.
For details on **why** you'd want to do this, see the [Kubernetes Authentication Guide](/kubernetes/oidc-authentication/).
@@ -33,7 +33,7 @@ Of course, it won't work yet, so there are a few tweaks we'll need..
#### Access Type
Change **Access Type** to `confidential` - this indicates to KeyCloak that your client can be trusted to keep a secret safe, and thus that secret can be used in the OIDC credentials exchange.
Change **Access Type** to `confidential` - this indicates to Keycloak that your client can be trusted to keep a secret safe, and thus that secret can be used in the OIDC credentials exchange.
![](/images/keycloak-kube-apiserver-2.png)