HTTP Basic Auth #26
Description
Problem statement
I'm running Navidrome behind an auth forwarding reverse proxy - authelia. This makes it so that client apps cannot talk to the API directly unless they pass the authentication. Browsers have no issue being redirected around. For this, authelia, and I assume many other auth proxies, allow authentication via HTTP basic auth which keeps the auth functional and non-browser clients that support it happy not having to implement vendor specific auth.
Proposed solution
Add optional HTTP basic auth config to the setup form. Use it when communicating with the API. Maybe alert the user when using basic auth without TLS.
Alternatives considered
Navidrome-internal auth with LDAP, but that's only possible if one already uses LDAP. Apparently that's not possible in vanilla Navidrome.
OAuth device auth flow - more complex in implementation
Scope
Backend integration