public/geek-cookbook
1
0
Fork 0
mirror of https://github.com/funkypenguin/geek-cookbook/ synced 2025-12-13 09:46:23 +00:00
Code Issues Releases Wiki Activity

Bump titles, fix 404s

Browse Source 
Signed-off-by: David Young <davidy@funkypenguin.co.nz>
This commit is contained in:
David Young
2022-07-06 06:08:44 +12:00
parent fcdd767241
commit 20ff12fd11
4 changed files with 15 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
manuscript/docker-swarm/traefik-forward-auth/dex-static.md
View File

@@ -1,8 +1,8 @@
---
title: Secure Traefik using Dex
title: SSO with traefik forward auth and Dex
description: Traefik forward auth needs an authentication backend, but if you don't want to use a cloud provider, you can setup your own simple backend, using Dex.
---
# Using Traefik Forward Auth with Dex (Static)
# Traefik Forward Auth for SSO with Dex (Static)
[Traefik Forward Auth](/docker-swarm/traefik-forward-auth/) is incredibly useful to secure services with an additional layer of authentication, provided by an OIDC-compatible provider. The simplest possible provider is a self-hosted instance of [CoreOS's Dex](https://github.com/dexidp/dex), configured with a static username and password. This recipe will "get you started" with Traefik Forward Auth, providing a basic authentication layer. In time, you might want to migrate to a "public" provider, like [Google][tfa-google], or GitHub, or to a [KeyCloak][keycloak] installation.

6
manuscript/docker-swarm/traefik-forward-auth/google.md
View File

@@ -1,8 +1,8 @@
---
title: Secure Traefik with Google Auth
description: Using Traefik Forward Auth, you can selectively secure your Docker services, using Google as your authentication backend!
title: SSO with traefik forward auth with Google Oauth2
description: Using Traefik Forward Auth, you can selectively apply SSO to your Docker services, using Google Oauth2 as your authentication backend!
---
# Traefik Forward Auth using Google
# Traefik Forward Auth using Google Oauth2 for SSO
[Traefik Forward Auth][tfa] is incredibly useful to secure services with an additional layer of authentication, provided by an OIDC-compatible provider. The simplest possible provider is a self-hosted instance of [Dex][tfa-dex-static], configured with a static username and password. This is not much use if you want to provide "normies" access to your services though - a better solution would be to validate their credentials against an existing trusted public source.

6
manuscript/docker-swarm/traefik-forward-auth/keycloak.md
View File

@@ -1,8 +1,8 @@
---
title: Secure Traefik using Keycloak
description: Traefik forward auth can selectively secure your Docker services against an authentication backend, and Keycloak is a perfect, self-hosted match.
title: SSO with traefik forward auth with Keycloak
description: Traefik forward auth can selectively SSO your Docker services against an authentication backend, and Keycloak is a perfect, self-hosted match.
---
# Using Traefik Forward Auth with KeyCloak
# Traefik Forward Auth with KeyCloak for SSO
While the [Traefik Forward Auth](/docker-swarm/traefik-forward-auth/) recipe demonstrated a quick way to protect a set of explicitly-specified URLs using OIDC credentials from a Google account, this recipe will illustrate how to use your own KeyCloak instance to secure **any** URLs within your DNS domain.

7
netlify_redirects.txt
View File

@@ -15,3 +15,10 @@ https://geek-cookbook.funkypenguin.co.nz/recipies/* https://geek-cookbook.funkyp
# Prefer "docker-swarm" to "ha-docker-swarm"
/ha-docker-swarm/* /docker-swarm/:splat 301!
# Old backlinks which we need to redirect to working URLs
/kubernetes/start/ /kubernetes/ 301!
/kubernetes/diycluster/ /kubernetes/cluster/ 301!
/recipes/autopirate/mylarr/ recipes/autopirate/mylar/ 301!