One interesting thing would be instead of relying on a database for the users and passwords would be to use OAUTH 2. Then aproxy could have a pure user/roles map and use the OAUTH 2 public key to verify the user instead of relying on a custom password database.
This is an OAUTH 2.0 / OIDC provider written in Go if this seems interesting: github.com/coreos/dex
One interesting thing would be instead of relying on a database for the users and passwords would be to use OAUTH 2. Then aproxy could have a pure user/roles map and use the OAUTH 2 public key to verify the user instead of relying on a custom password database.
This is an OAUTH 2.0 / OIDC provider written in Go if this seems interesting: github.com/coreos/dex