fix: IBM Cloud Secrets Manager Imported Cert does not always require intermediate cert#5370
Conversation
…ediate cert Signed-off-by: Varnika Sinha <varnsinha@gmail.com>
Signed-off-by: Varnika Sinha <varnsinha@gmail.com>
f7ad7d6 to
6420f51
Compare
…imported cert Signed-off-by: Varnika Sinha <varnsinha@gmail.com>
Signed-off-by: Varnika Sinha <varnsinha@gmail.com>
TestingThis testing has been conducted in a development IBM Cloud environment, so some information has been redacted due to security reasons. Before the ESD definition I was using was Built the image with the changes on this PR locally and pushed it to my team's local registry and edited the deployment of External Secrets we have running our kubernetes cluster to use the new image After Can confirm the External Secrets definition created a new secret with the correct values as reflected in the SM instance |
|
…intermediate cert (external-secrets#5370) * fix: IBM Secrets Manager Imported Cert does not always require intermediate cert Signed-off-by: Varnika Sinha <varnsinha@gmail.com> * Fixing error messages Signed-off-by: Varnika Sinha <varnsinha@gmail.com> * Addressing feedback for comment about skipping intermediate cert for imported cert Signed-off-by: Varnika Sinha <varnsinha@gmail.com> * Fixing typo of immediate cert -> immediate certificate to be clear Signed-off-by: Varnika Sinha <varnsinha@gmail.com> --------- Signed-off-by: Varnika Sinha <varnsinha@gmail.com> Co-authored-by: Gergely Brautigam <skarlso777@gmail.com> Signed-off-by: Samuel Molling <samuelmolling@gmail.com>



Problem Statement
In IBM Cloud Secrets Manager, when you create an imported cert, the intermediate and private key is not required to be provided and is listed as optional.

As a user of the plugin, we created a imported cert type with a certificate and private key, but no intermediate cert. Our ESO component which is a direct mirror of this repo gave us the error
Searching through this repo, we realized that the plugin expects intermediate certificate to be there even when the UI as shown above and the documentation don't list it as a required field for this kind of secret type.
Related Issue
Fixes #5371
Proposed Changes
How do you like to solve the issue and why?
I would like the ESO plugin for IBM Cloud Secrets Manager to follow what its documentation mentions to its users. My team at IBM uses this plugin to manage imported certs, and we need this available where intermediate certs are not required.
Format
Please ensure that your PR follows the following format for the title:
Where
scopeis optionally one of:Checklist
git commit --signoffmake testmake reviewable