Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Any form of authentication #12

Open
martin-braun opened this issue Aug 13, 2022 · 2 comments
Open

Any form of authentication #12

martin-braun opened this issue Aug 13, 2022 · 2 comments

Comments

@martin-braun
Copy link

For a self-hosted solution, I would welcome to have the ability to config several credentials that need to be put in in order to use the website / API. This would also completely solve #9 on private instances.

@somenonymous
Copy link
Owner

It's a doable idea, but I'll postpone it for now, unless you want to make a PR.

@kkarhan
Copy link

kkarhan commented Apr 12, 2023

Can't said reverse-proxies handle HTTP-AUTH with a simple user/password or token?

This is quite a common approach with a lot of web-based applications and espechally when using ngnix as sanitizer for SQL queries to stop low-level skiddies and bots.

Same with rate-limiting: If I were to seriously host this, I'd propably limit the packet rate or bandwith per connection / IP to something in the ream to 10MBit/s - 100 MBit/s maximum via either the transparent proxy or some MITM "firewall" / "load-balancer" appliance [yes that is ugly but too bad big corporate IT is messy!]...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants