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 corporate DNS records for Vault Validation #54

Open
webmutation opened this issue Feb 2, 2021 · 0 comments
Open

Support corporate DNS records for Vault Validation #54

webmutation opened this issue Feb 2, 2021 · 0 comments

Comments

@webmutation
Copy link

webmutation commented Feb 2, 2021

So this is probably not an easy question...
After reading and testing Using SPIRE and OIDC to Authenticate Workloads to Retrieve Vault Secrets
it works well. However my use case, probably similar to many others, is that our clusters are not exposed to the public network. They do have a DNS entry, usually in our case a nginx RP mapping.

I noticed that on the oidc-discovery-provider.conf its using https://acme-v02.api.letsencrypt.org/directory, would it be possible to replace this with a local option?

Where can I find more details about gcr.io/spiffe-io/oidc-discovery-provider

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant