Caleb Doxsey

We can update the code to use the `fsnotify` package. I don't remember why we used the `notify` package.

This is a result of https://github.com/pomerium/pomerium/pull/1739. I don't know how to fix it.

This was fixed with https://github.com/pomerium/pomerium/pull/3596. We should no longer return 421s.

This issue is not resolved but if we feel like it is not needed I will close it.

The new API appears to require more credentials than we currently use. I keep getting a 401 for `/api/2/users` even though `/api/1/users` works properly. This API is still in development,...

Unfortunately there's not really any good solution to this problem. Ways to fix it: 1. Add all the routes to every domain 2. Use different TLS certificates for each shared...

Moving to the icebox until we have a better solution.

Hi @muscovitebob , IP whitelists or blacklists can be implemented in Pomerium using an external data source (an enterprise feature). For example we maintain a list of Tor Exit Nodes...

Agreed that this would be valuable. It's slightly complicated because we have a layered configuration where there can be multiple configuration sources on top of each other. The most common...

We could support wildcards but not like some of the examples given above. We are limited to what Envoy supports: > The server name will be matched against all wildcard...