oauth2-proxy
Architectural problems with the alpha secret
I think the -oauth2-proxy-alpha has a couple of questionable design decisions
I don't understand why we're storing the secret for alphaAuth as b64. Why not just store it as yaml? It makes sense when you're storing toml. But it doesn't make sense when the actual file is yaml. If it's valid yaml to begin with we don't have to worry about it not being valid yaml there.
I don't think we write out one file with all the secrets.. These should be mapped to environmental variables instead. Atleast the clientIds, and clientSecrets.
@tuunit, isn't this a question about the software more than the chart? Shouldn't it be moved to the other repo?
There is a project to refactor alphaConfig, which should resolve all related issues. I would appreciate your patience.
Ref:
- https://github.com/oauth2-proxy/manifests/issues/226
- https://github.com/oauth2-proxy/manifests/issues/302
- https://github.com/oauth2-proxy/manifests/issues/311