-
Notifications
You must be signed in to change notification settings - Fork 552
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
internal/util/vault.go passes incorrect type for vaultCAVerify #1852
Labels
Comments
nixpanic
added
bug
Something isn't working
component/util
Utility functions shared between CephFS and RBD
labels
Feb 2, 2021
nixpanic
added a commit
to nixpanic/ceph-csi
that referenced
this issue
Feb 2, 2021
The configuration option `EnvVaultInsecure` is expected to be a string, not a boolean. By converting the bool back to a string (after verification), it is now possible to skip the certificate validation check by setting `vaultCAVerify: false` in the Vault configuration. Fixes: ceph#1852 Reported-by: Bryon Nevis <[email protected]> Signed-off-by: Niels de Vos <[email protected]>
mergify bot
pushed a commit
that referenced
this issue
Feb 2, 2021
The configuration option `EnvVaultInsecure` is expected to be a string, not a boolean. By converting the bool back to a string (after verification), it is now possible to skip the certificate validation check by setting `vaultCAVerify: false` in the Vault configuration. Fixes: #1852 Reported-by: Bryon Nevis <[email protected]> Signed-off-by: Niels de Vos <[email protected]>
mergify bot
pushed a commit
that referenced
this issue
Feb 2, 2021
The configuration option `EnvVaultInsecure` is expected to be a string, not a boolean. By converting the bool back to a string (after verification), it is now possible to skip the certificate validation check by setting `vaultCAVerify: false` in the Vault configuration. Fixes: #1852 Reported-by: Bryon Nevis <[email protected]> Signed-off-by: Niels de Vos <[email protected]> (cherry picked from commit 582d004)
mergify bot
pushed a commit
that referenced
this issue
Feb 2, 2021
The configuration option `EnvVaultInsecure` is expected to be a string, not a boolean. By converting the bool back to a string (after verification), it is now possible to skip the certificate validation check by setting `vaultCAVerify: false` in the Vault configuration. Fixes: #1852 Reported-by: Bryon Nevis <[email protected]> Signed-off-by: Niels de Vos <[email protected]> (cherry picked from commit 582d004)
nixpanic
added a commit
to nixpanic/ceph-csi
that referenced
this issue
Feb 2, 2021
The configuration option `EnvVaultInsecure` is expected to be a string, not a boolean. By converting the bool back to a string (after verification), it is now possible to skip the certificate validation check by setting `vaultCAVerify: false` in the Vault configuration. Fixes: ceph#1852 Reported-by: Bryon Nevis <[email protected]> Signed-off-by: Niels de Vos <[email protected]> (cherry picked from commit 582d004)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Describe the bug
The
initConnection()
method ininternal/util/vault.go
stores a boolean value invaultConfig["VAULT_SKIP_VERIFY"]
butgithub.com/libopenstorage/secrets
expects configuration values to be strings.Environment details
fuse
orkernel
. for rbd itskrbd
orrbd-nbd
) : rbdSteps to reproduce
Steps to reproduce the behavior:
Create ceph-csi-encryption-kms-config config map with TLS-based Vault and "vaultCAVerify": "false" while using encryption enabled RBD storage pool.
Actual results
Provisioner plugin raises exception that the Vault TLS certificate cannot be verified, regardless of the setting of vaultCAVerify.
Expected behavior
Vault connection is made without supplying custom CA when vaultCAVerify is false.
Logs
csi-provisioner log
Additional context
See related ticket for a fuller description of the issue:
libopenstorage/secrets#51
Suggested change:
Change
to
The text was updated successfully, but these errors were encountered: