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

Unable to switch to use KMIP as Encryption Key Vault #19

Closed
keithlcs opened this issue Sep 25, 2024 · 2 comments · Fixed by #20
Closed

Unable to switch to use KMIP as Encryption Key Vault #19

keithlcs opened this issue Sep 25, 2024 · 2 comments · Fixed by #20

Comments

@keithlcs
Copy link

Hello

I have just procured a new Synology NAS using DSM 7.2.2-72806, with KMIP config using the kmip-server-dsm according to the guide. Yet, I have experienced a strange problem. The NAS could able to make a KMIP connection under the "Control Panel > Security > KMIP" section in DSM, but unable to select KMIP under the "Storage Manager > Global Settings > Reset Encryption Key Vault" section.

Success Import Client Cert:
Screenshot 2024-09-26 at 06 35 03

Success KMIP server connection:
Screenshot 2024-09-26 at 06 35 23

Not able to switch to KMIP for Encryption Key Vault:
Screenshot 2024-09-26 at 06 36 01

Below is the pykmip config.sh and server.conf
config-sh.txt

server-conf.txt

And I could not find any errors in the server.log, below is the extract:
extract-server.log

Are there any issues in my settings or configuration which lead to such strange problem?

Thanks in advance. :)

@rnurgaliyev
Copy link
Owner

Thank you for reporting this. It seems that breaking change was introduced in #16. I've rolled back pykmip to v0.10.0 for now. You should be able to setup remote encryption vault now, if you pull latest release and rebuild the docker container.

I will have more time in October to have a deeper look at the issue and make further updates of pykmip possible. cc @oittaa

@keithlcs
Copy link
Author

Hi rnurgaliyev, thank you for your help.
I have tried to rebuild the container based on v2024.9.2, and the strange problem has been resolved.

Thanks. :)

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

Successfully merging a pull request may close this issue.

2 participants