caddy-security VS vouch-proxy

There is no "refusal" as far as I can tell. The issues were reported [1] in September 2023 (as was this blog post) and the simplest one has been fixed (insecure random seed). I'm not aware of any public statements from the plugin maintainers, and there is no hostility in the issue comments.

[1]: https://github.com/greenpau/caddy-security/issues?q=is%3Aiss...

> September 18, 2023: The disclosure blog post was released and issues were filed with the original project repository.

I don't see those issues listed in the GitHub project issue tracker https://github.com/greenpau/caddy-security/issues. Have they been deleted?

Check out https://github.com/greenpau/caddy-security

There a pretty comprehensive auth plugin for Caddy. It can do local authentication with a session cookie, which should work with your IPTV apps. If your app can show a login form, it's super easy, but if I remember correctly you can also authenticate with basic auth and store the session in a cookie (this is mostly used to carry over the authentication to a different subdomain).

I use Caddy + Caddy Security, set up OAuth, and also only expose services over IPv6. It's not extra security, but it's less logs to deal with because nobody is scanning IPv6 address ranges, and there are less IPv6 capable hosts who are compromised.

Not sure if this fits your bill, but have a look at Caddy web server and its available authentification methods or even more with a plugin

Also look at github.com/greenpau/caddy-security to enable MFA for Caddy.

- Guacamole docker connects to Debian VNC Desktop - Caddy docker offers HTTPS proxy with Guacamole and the Caddy Security plug in for Auth with TOTP

Look into vouch proxy

Vouch proxy is designed for this usage: https://github.com/vouch/vouch-proxy I don't think there are any nice UIs to configure it though so you'll need to be familiar with running it yourself.

Not sure this is a "best practice", but it lets me keep control of the Ingress resources inside their YAML configs. I've also layered Vouch Proxy into the ingress configurations to require SSO/MFA auth to access the resources behind the Ingress. Cloudflare has the ability to do this, but I found it cumbersome to keep track of the configs outside the K8s cluster.

I've used vouch proxy for my own stuff previously, before more recently moving to Cloudflare Access. vouch can be slightly janky at times to get working right, but once set up, it's been solid.

For example: nginx -> Vouch proxy -> KeyCloak -> Jellyfin

While this works, we were hoping to make access a bit easier with say an OpenID Connect SSO and reverse-proxy solution. I've seen Vouch Proxy, https://github.com/vouch/vouch-proxy which is really just SSO on top of nginx, but I'm wondering if there's a simpler way to do this.

You seem to be quite knowledgeable and a minimal provider with just the bare minimum would suffice for you. Have a look at Vouch Proxy, it does one thing and it does it well.