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

Add support for X509_PROVIDED #35

Open
f-blass opened this issue Dec 6, 2021 · 2 comments
Open

Add support for X509_PROVIDED #35

f-blass opened this issue Dec 6, 2021 · 2 comments

Comments

@f-blass
Copy link
Member

f-blass commented Dec 6, 2021

The buildpack downloads the Authorization Bundle and authenticates with the Identity certificate.
In case of the credential type X509_GENERATED the Identity Broker generates a certificate and key and puts it into the binding.

In case of X509_PROVIDED this is not the case and the application needs a way to provide the private key (and cert) to the application.
This could be done via env variable, user-provided service, something else…?

@d047491
Copy link
Contributor

d047491 commented Jan 4, 2022

This is quite easy to implement. The cert is still contained in the binding, only the key should be provided in another way. The challenge is to align with other components in providing this key. If anyone has an idea, please let us know

@nenaraab
Copy link
Contributor

nenaraab commented Jan 4, 2022

I have no answer on how applications normally shall provide the key to the environment, but we should also support external keys as part of our go client lib.

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

3 participants