⚡️ Feature: add support for authentication through request headers from reverse proxy

[piejanssens]

Feature Description

https://tinyauth.app/docs/reference/headers/#remote-user

Problem It Solves

Supports setups with a reverse proxy that manages authentication directly or through routing middleware such as Authentik, TinyAuth, Authelia, ...

Proposed Solution

Allow configuration of a request header that contains the username.

Alternatives Considered

No response

Additional Context

This is safe when the reverse proxy is the only way to access Arcane (e.g. port is not exposed outside of docker).

Would you be willing to work on this feature?

• Yes, I'd like to implement this feature
• I could help with parts of this feature
• No, I'm just suggesting the feature

[piejanssens]

I am closing this feature request after setting up OIDC with Tinyauth which is giving me exactly what I need.

Tip for other users:

• Use the admin claim mapping, e.g. claim preferred_username, value <your tinyauth username>
• Enable "Auto Redirect to Provider" to skip the Arcane native login screen

@kmendell FYI