enhancement - reverse proxy chaining?

[c-nv-s]

Is there a possibility to place Vaulty in front of another reverse proxy such as HAProxy or Caddy and then pass on the X-Forwarded-For Header so that the following proxy is still aware of the original client?

[alovak]

Hey, @c-nv-s! thanks for your question. Currently, it's not implemented, but I can add it.

Do you use Vaulty or plan to use it in production? It would be great to know that someone uses it :)

[c-nv-s]

Yes i'm testing it now and would love to use it in production

[c-nv-s]

I think what might also be nice is if you could facilitate encryption based on "dynamic public keys".
So you could have a dictionary of X-Vaulty-APIKey header to public key e.g.

{
"00001" : "ssh-rsa AAAAB3NzaC1yc2EAAAADAQAB....",
"00002" : "ssh-rsa AAAAC5DslFj2alDBBB3NZC1B.....",
...
}

so when the request comes in, Vaulty would see the value of X-Vaulty-APIKey: 00002 and encrypt the value using "ssh-rsa AAAAC5DslFj2alDBBB3NZC1B....."

and an admin endpoint you can call to add/delete public keys to the list