Firefly Server behind Traefik BasicAuth

[mgorfer]

Firefly Server behind Traefik BasicAuth

[dreautall]

After looking into it some more, this is NOT possible, sorry.

Both OAuth and Basic Auth use the same Authorization HTTP header, which might only be submitted once.

The "easy" way would be to un-protect calls to /api/ from your basic auth configuration (all calls from Waterfly are going to the API, it never requests a resource outside of that path). You can keep the Basic Auth for the normal Webinterface then.

[dreautall]

I have Firefly directly on the Internet without BasicAuth in front, mainly because Firefly has its own authentication anyways.

But regardless of that, Waterfly should work in all settings! Just a quick (untested) idea, what happens if you use https://user:[email protected] (with user & pass obviously replaced) as the domain?

If that doesn't work, I'll add it to the list of things to implement :)

[mgorfer]

I added the BasicAuth, because I thought double the security cannot hurt. But you are right, I could just switch it off. waterfly-iii works flawlessly in that condition.

I tried your idea. It is working in my browser, to directly reach the login page of firefly. It is not working in waterfly-iii though. I am getting the same error as before.

I would be glad if you could add an option to access the firefly server through BasicAuth, but I will just turn off the BasicAuth for now.
So that Feature Request has very low priority from my side :)

[mgorfer]

Thank you for the update!
I will try to implement your suggestion on my side.

[ahatdude]

Thank you for the update! I will try to implement your suggestion on my side.

I apologise for revisiting this old issue, but @mgorfer would you be kind enough to explain to me how you added this exception to the firefly container? I'm on unraid and I'm having trouble knowing what I should be adding as a label or what I should be changing in the config to allow Waterfly to access my server with no issue.

Thanks :-)