Cannot pass Basic Authentication header with https request

[forestial]

My Jellyfin server is 'behind' a reverse proxy implemented with Nginx Proxy Manager. This allows me to have use an external https URL and still be able to access the server from outside my home network. I just enter the https:// URL at the finamp login, along with my Jellyfin username and password, and this works fine.

I would like to also add a username/password (Basic Authentication) to control access to this https address. With other https clients I can do this by adding an Authorization header and base64-encoding the credentials, something like Authorization: Basic YWxhZGRpbjpvcGVuc2VzYW1l

I cannot see a way to add the Authorization header at the finamp login. Is this possible? Do I instead need to embed the username:password (unencoded) in the URL itself?

I am using the IOS client version 0.6.25

[Chaphasilor]

Hey! There currently is no way to manually add an authorization header, but that is something we could add.
Embedding the auth in the URL itself probably won't work, but feel free to try :)

[forestial]

Yes, you're correct: passing creds in the URL itself doesn't work. Thanks for considering supporting the headers in future.

[gpatkinson]

+1

[oxidand]

I would also be interested in this feature. Without it, I have to expose Jellyfin to the public, which is not ideal.

[aromatictoast]

Same here! That would be really useful. I currently have a setup using a cloudflare tunnel which is secured using an OAuth flow, meaning Finamp can't connect. If we had a way give finamp service tokens to send with requests that would be really helpful!