coop-cloud/traefik
6
2
Fork 19
Code Issues 14 Pull Requests 7 Releases Wiki Activity

How to configure a second traefik-forward-auth on the same traefik instance? #30

New Issue
Closed
opened 2021-11-20 13:09:00 +00:00 by 3wordchant · 0 comments
3wordchant commented 2021-11-20 13:09:00 +00:00
Owner
Copy Link
Copy Source

Let's say we have swarm.example.com, running:

  • id.project.org (Keycloak)
  • secret.project.org (custom-html)
  • id.otherproject.org (Keycloak)
  • secret.otherproject.org (custom-html)

We want secret.project.org to require id.project.org login, and secret.otherproject.org to require id.otherproject.org login.

Currently, we can deploy two coop-cloud/traefik-forward-auth instances with different stack names, and configure them to point at the two Keycloak instances.

But! There's no way to tell Traefik about the second instance, because we only have one "slot" for an auth middleware.

One approach could be to duplicate that section, and have e.g. KEYCLOAK_MIDDLEWARE_2_ENABLED variable, keycloak2 middleware. This would (I think!) work fine for this specific case, but scaling to supporting a 3rd, 4th etc traefik-forward-auth would be increasingly annoying.

Is there any better way to define a variable set of auth middlewares?

Let's say we have swarm.example.com, running: - `id.project.org` (Keycloak) - `secret.project.org` (custom-html) - `id.otherproject.org` (Keycloak) - `secret.otherproject.org` (custom-html) We want `secret.project.org` to require `id.project.org` login, and `secret.otherproject.org` to require `id.otherproject.org` login. Currently, we can deploy two coop-cloud/traefik-forward-auth instances with different stack names, and configure them to point at the two Keycloak instances. But! There's no way to tell Traefik about the second instance, because [we only have one "slot" for an auth middleware](https://git.coopcloud.tech/coop-cloud/traefik/src/branch/master/file-provider.yml.tmpl#L4-L10). One approach could be to duplicate that section, and have e.g. `KEYCLOAK_MIDDLEWARE_2_ENABLED` variable, `keycloak2` middleware. This would (I think!) work fine for this specific case, but scaling to supporting a 3rd, 4th etc `traefik-forward-auth` would be increasingly annoying. Is there any better way to define a variable set of auth middlewares?
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
Something is not working
 duplicate
This issue or pull request already exists
 enhancement
New feature
 help wanted
Need some help
 invalid
Something is wrong
 question
More information is needed
 wontfix
This won't be fixed
No labels
Milestone
No items
No Milestone
Assignees
Clear assignees
3wordchant aadil (Aadil Ayub) abra-bot (Abra Bot) ammaratef45 amras (Sarma) BornDeleuze Brooke carla cas (Cassowary) coopcloud decentral1se (d1) fauno (fauno) javielico (Javielico) jjsfunhouse kawaiipunk (KawaiiPunk) knoflook moosemower moritz notplants oxaliq (sorrel) p4u1 renovate-bot (Comrade Renovate Bot) simon stevensting trav (Trav Fryer) yksflip
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: coop-cloud/traefik#30