Skip to content

Architectural problems with the alpha secret #302

@EvanCarroll

Description

@EvanCarroll

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions