Future of traefik-forward-auth

[nOw-Ay]

Hello,

Above all I want to thanks @thomseddon for all his work on traefik-forward-auth. This discussion does not have for purpose to pressure him in any way but rather to find solutions.

As you surely noticed, Tom's activity these last years has been disparate, which is understandable : maintaining an open source project (mostly) alone is a huge, time consuming task.

The main issue is that mature, working pull requests are no longer merged which causes frustration. Being a "silent" user of traefik-forward-auth, I did not particularly mind this fact until I found myself missing features that are actually pending for a simple merge. We began discussing this a little bit in this PR.
Using the draft of propositions and discussions that we have, I distinguish three options :

• @thomseddon comes back one day, PR can finally be merged, the issue is solved.

• @thomseddon comes back and accept, if he wants to, to distribute access rights between a group of motivated and experienced users on which he can relies on.

• In last resort, a group of motivated users decides to create and maintain a fork of traefik-forward-auth. This should really be the last path to be taken since other projects in the past found themselves destroyed by such divisions. But it may be necessary if @thomseddon does not intend to come back or distribute access rights.

I open this discussion to potentially allow the formation of this potential small group of "motivated and experienced" users and, I hope, to get an answer from @thomseddon and move forward.

Thanks a lot for your time and dedication.

[nOw-Ay]

It's been a year since my last message, nothing much has changed on my end.

I wanted to share @ItalyPaleAle's alternative. It started as a fork but has since evolved into a separate project that's well-documented and actively maintained.

EDIT: ItalyPaleAle implemented RBAC/GBAC in v4. It seems to be a pretty solid solution :-D