Add a slot for a second traefik-forward-auth #31
No reviewers
Labels
No Label
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: coop-cloud/traefik#31
Loading…
Reference in New Issue
No description provided.
Delete Branch "forward-auth-2"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Closes #30
Situation:
auth.example.com
on a server, let's sayswarm.example.com
, to put sites behind a Keycloak login, e.g.id.example.com
id.client.com
swarm.example.com
behind the second Keycloak login.This patch adds a second "slot" for a traefik-forward-auth, by defining a
keycloak2
middleware.Seems to be working fine so far;
login.vrec.coop
is behindid.vrec.coop
login, on the same server as other sites protected byid.autonomic.zone
.Obviously no help whatsoever if people need to add a THIRD traefik-forward-auth, but at least it solves the immediate need 🤷
🚀