It's not really "piling on more complexity". I already have a well-configured OIDC provider that already handles a lot of home lab software that supports OIDC n

It's not really "piling on more complexity". I already have a well-configured OIDC provider that already handles a lot of home lab software that supports OIDC natively. For things not supporting OIDC natively there's OIDC Proxy for traefik. So in this case the solution is adding a label requesting the OIDC Proxy Middleware, and adding a redirect URL to the OIDC application. You could argue that it's "more complexity", but routing it through a home vpn, for instance, is also "more complexity". What, in your opinion is "simple, performant, and sane"? You casually throw that around, but never explain...