Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support specifying client TLS certificate #35

Closed
travisgroth opened this issue Feb 3, 2022 · 2 comments
Closed

Support specifying client TLS certificate #35

travisgroth opened this issue Feb 3, 2022 · 2 comments
Assignees
Labels
enhancement New feature or request

Comments

@travisgroth
Copy link
Contributor

Is your feature request related to a problem? Please describe.

We currently support two subcommands that make a request to services that are behind the Pomerium Proxy. However, neither command accepts a client TLS cert and key when making the underlying HTTP connection.

In some environments, client certificates function as stand ins for device state or other inventory based controls, but these don't currently work with the tcp and k8s subcommands.

Describe the solution you'd like

Support passing a TLS certificate and key file path as command line flags to both tcp and k8s commands.

Describe alternatives you've considered

n/a

Explain any additional use-cases

The desktop client will also need to support this for tcp tunnels.

Additional context

Related pomerium/pomerium#2983

@travisgroth
Copy link
Contributor Author

/cc @cfanbo

@wasaga
Copy link
Contributor

wasaga commented Feb 8, 2022

Per internal discussion - we will not support password protected keys

@wasaga wasaga mentioned this issue Feb 9, 2022
6 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants