1
0
mirror of https://github.com/funkypenguin/geek-cookbook/ synced 2025-12-13 01:36:23 +00:00

Updated the docker image that is used to the fork (#62)

Updated the docker image that is used to the fork for people like me who just copy paste the big code blocks without reading :>
This commit is contained in:
Thomas
2019-11-11 12:38:27 +13:00
committed by David Young
parent 4f4a9f751c
commit e0c529855e

View File

@@ -52,7 +52,7 @@ This is a small container, you can simply add the following content to the exist
```
traefik-forward-auth:
image: thomseddon/traefik-forward-auth
image: funkypenguin/traefik-forward-auth
env_file: /var/data/config/traefik/traefik-forward-auth.env
networks:
- traefik_public
@@ -113,4 +113,4 @@ What have we achieved? By adding an additional three simple labels to any servic
1. Traefik forward auth replaces the use of [oauth_proxy containers](/reference/oauth_proxy/) found in some of the existing recipes
2. [@thomaseddon's original version](https://github.com/thomseddon/traefik-forward-auth) of traefik-forward-auth only works with Google currently, but I've created a [fork](https://www.github.com/funkypenguin/traefik-forward-auth) of a [fork](https://github.com/noelcatt/traefik-forward-auth), which implements generic OIDC providers.
3. I reviewed several implementations of forward authenticators for Traefik, but found most to be rather heavy-handed, or specific to a single auth provider. @thomaseddon's go-based docker image is 7MB in size, and with the generic OIDC patch (above), it can be extended to work with any OIDC provider.
4. No, not github natively, but you can ferderate GitHub into KeyCloak, and then use KeyCloak as the OIDC provider.
4. No, not github natively, but you can ferderate GitHub into KeyCloak, and then use KeyCloak as the OIDC provider.