Geri Jennings

Yes! My problem statement still assumes the use of the env var - it may more generally be stated as > When I deploy and configure Conjur with a given...

sure. it's really about revising the configuration once it's up and running, which could be solved any number of ways (but maybe most usefully by providing alternate ways to configure...

Just noting here that we now have documentation on how to update environment variables once Conjur is already deployed: - [Using the helm chart](https://github.com/cyberark/conjur-oss-helm-chart/tree/master/conjur-oss#modifying-environment-variables-for-an-existing-conjur-oss-helm-deployment) - [Using the `docker-compose` cluster](https://github.com/cyberark/conjur-quickstart/#adding-or-modifying-container-environment-variables)

@jonahx is this still something we plan on doing? I think this isn't critical near-term, so I'm inclined to move it back to the icebox for now.

It looks like to implement these we'd need to - Update the Conjur server to provide a configuration option for the `DefaultClientCertPath` for authn-k8s, with the default value if no...

it looks like the authn-k8s client explicitly sets the `content-type` here: https://github.com/cyberark/conjur-authn-k8s-client/blob/922126ad8d603fc7ce32ac76a2eeee0ef5667205/pkg/authenticator/requests.go#L29 ETA it's also (on the line below the line linked above) setting a custom `Host-Id-Prefix` header - which...

I think we could add this support soon, and I propose we do it using option (3) - "Certificate install path may be provided using the `Certificate-Install-Path` header" to be...

Tagging in @diverdane, since I know he's been experimenting with troubleshooting this sort of setup using the helm chart.

labeled as `good-first-issue` in case someone wants to take on trying to write the generic HTTP config for this :)

@dsbyrne @kgilpin is this still something you're thinking we'll consider? If not, can we close this issue?