To Add Users or not?

reven

Need some feedback on this feature.

Do you want to lock fileflows behind a username/password, or left open to anyone who can access your network?

Please vote on this ticket with either a thumbs up for yes, and a thumbs down for no.

https://github.com/revenz/FileFlows/issues/369

I'll unlikely make it optional, it will either be added and enforced (password length wont be enforced, so could just be username with blank password), or not add it at all. If added will likely add support for single sign on using google etc (similar to what fenrus does)

Yankees4life

If the aim is using FF for reverse proxies, then yeah but honestly I don't like putting my stuff out there to the internet (don't want to risk being exposed online) so it should be optional.

Not too sure how many people is gonna use FF with a reverse proxy anyways compared to the Arrs/qbit/sabnzbd/jellyfin/etc...

reven

optional opens to many security concerns. so it would be I'll do it or I won't thing.

I won't do it until there is a large number of votes on the ticket and it's highly in favor of adding it.

Honestly, its one of those things where entering admin/admin [remember me] is not much effort and for those who want it for other reasons do tip the scales in favour of adding it.

But if 90% of users dont want it, then I'll probably not do it, and direct those 10% of users to authelia or something

Beardo

I say yes. I'm one of those that chucks everything behind reverse proxies with SSL certificates and ip whitelists. I access from a lot of different common places and using a .htaccess to lock it further by login is annoying. a proper login form would go a long way to simplifying.

reven

There doesnt seem to be a lot of demand for this currently, so I won't be adding this in the near future. If demand for this grows, ill look into adding it.