Basic Authentication for Porter#2726
Conversation
|
I am thinking that a very common use case for Porter will require CORS "allow-origin" style access control. Essentially the ability to whitelist domains that requests are allowed to come from. Similar to how Infura's "Allowlist Origins" work. So people will be able to make websites and run a porter server to service them. I guess this would be doable through an nginx proxy. Have we talked about all this? |
7220661 to
5a90d4e
Compare
@vepkenez the question becomes what do we provide out of the box vs what do we leave for people who intend to run Porter to customize for their own needs. As you mentioned, some of the more intricate functionality can be obtained via nginx proxy sitting in front of Porter, so we should think of where to draw the line. Let's chat more tomorrow. |
Type of PR:
Required reviews:
What this does:
Based over #2724 .
Allows Porter to facilitate Basic Authentication over HTTPS based on a provided
htpasswdfile via--basic-auth-filepath. Updated Docker/docker-compose files accordingly.Issues fixed/closed:
Fixes #2706 - does it fully "fix" it? perhaps for now unless users decide they want something more robust. However, this is a good starting point.
Why it's needed:
User authentication in some form will be needed if Porter is to be used as a public service.