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

Add authentik, tidy up recipe-footer

Browse Source 
Signed-off-by: David Young <davidy@funkypenguin.co.nz>
This commit is contained in:
David Young
2023-10-31 14:37:29 +13:00
parent 0378e356fe
commit f22dd8eb50
142 changed files with 805 additions and 708 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/docker-swarm/traefik-forward-auth/dex-static.md
View File

@@ -203,4 +203,4 @@ What have we achieved? By adding an additional label to any service, we can secu
[^1]: You can remove the `whoami` container once you know Traefik Forward Auth is working properly
--8<-- "recipe-footer.md"
{% include 'recipe-footer.md' %}

2
docs/docker-swarm/traefik-forward-auth/google.md
View File

@@ -133,4 +133,4 @@ What have we achieved? By adding an additional three simple labels to any servic
[^1]: Be sure to populate `WHITELIST` in `traefik-forward-auth.env`, else you'll happily be granting **any** authenticated Google account access to your services!
--8<-- "recipe-footer.md"
{% include 'recipe-footer.md' %}

2
docs/docker-swarm/traefik-forward-auth/index.md
View File

@@ -52,6 +52,6 @@ Traefik Forward Auth needs to authenticate an incoming user against a provider.
* [Authenticate Traefik Forward Auth against a whitelist of Google accounts][tfa-google]
* [Authenticate Traefik Forward Auth against a self-hosted Keycloak instance][tfa-keycloak] with an optional [OpenLDAP backend][openldap]
--8<-- "recipe-footer.md"
{% include 'recipe-footer.md' %}
[^1]: Authhost mode is specifically handy for Google authentication, since Google doesn't permit wildcard redirect_uris, like [Keycloak][keycloak] does.

2
docs/docker-swarm/traefik-forward-auth/keycloak.md
View File

@@ -100,4 +100,4 @@ What have we achieved? By adding an additional three simple labels to any servic
[KeyCloak][keycloak] is the "big daddy" of self-hosted authentication platforms - it has a beautiful GUI, and a very advanced and mature featureset. Like Authelia, KeyCloak can [use an LDAP server](/recipes/keycloak/authenticate-against-openldap/) as a backend, but _unlike_ Authelia, KeyCloak allows for 2-way sync between that LDAP backend, meaning KeyCloak can be used to _create_ and _update_ the LDAP entries (*Authelia's is just a one-way LDAP lookup - you'll need another tool to actually administer your LDAP database*).
--8<-- "recipe-footer.md"
{% include 'recipe-footer.md' %}