2017-11-26 22:06:28 +0200 | received badge | ● Famous Question (source) |
2017-02-21 18:08:15 +0200 | received badge | ● Notable Question (source) |
2017-02-19 05:27:20 +0200 | commented answer | Openstack ConfigWinRMCertificateAuthPlugin CryptoAPI error Hi, any pointers on what could be the issue? |
2017-02-11 01:13:53 +0200 | commented answer | Openstack ConfigWinRMCertificateAuthPlugin CryptoAPI error I'm also wondering why in the blog post in https://cloudbase.it/windows-without-passwords-in-openstack/ it is suggested to convert the PEM to a DER and base 64 encode it, since windows recognizes both PEM and DER. |
2017-02-10 23:29:16 +0200 | commented answer | Openstack ConfigWinRMCertificateAuthPlugin CryptoAPI error Hi Adrian, thanks for response. I've added the details to the original post. Though I don't have the configwinrmcertificateauthplugin listed in the configuration, it does appear to trigger it, as seen from the log file |
2017-02-10 23:17:31 +0200 | received badge | ● Editor (source) |
2017-02-10 23:12:43 +0200 | received badge | ● Popular Question (source) |
2017-02-09 04:01:18 +0200 | asked a question | Openstack ConfigWinRMCertificateAuthPlugin CryptoAPI error Hi, I would like to add a X509 auth certificate to the Windows server running on Openstack so I can execute WinRM commands using a cert rather than a password. When bringing up a server instance, I'm passing the x509 cert as meta data as we use the user data to execute PS commands. I construct the metadata as shown in this post: https://cloudbase.it/windows-without-... The Windows image used is derived from Windows 2012R2 eval images from Cloudbase, and the ConfigWinRMCertificateAuthPlugin appears to pick up the passed cert. The only difference is that we generate our own pem cert. However, I see the following error in the console log: 2017-02-07 09:07:56.735 1984 ERROR cloudbaseinit.init [-] plugin 'ConfigWinRMCertificateAuthPlugin' failed with error 'CryptoAPI error: 0xd' 2017-02-07 09:07:56.750 1984 ERROR cloudbaseinit.init [-] CryptoAPI error: 0xd 2017-02-07 09:07:56.750 1984 ERROR cloudbaseinit.init Traceback (most recent call last): 2017-02-07 09:07:56.750 1984 ERROR cloudbaseinit.init File "c:\program files\cloudbase solutions\cloudbase-init\python\lib\site-packages\cloudbaseinit\init.py", line 75, in execplugin 2017-02-07 09:07:56.750 1984 ERROR cloudbaseinit.init shareddata) 2017-02-07 09:07:56.750 1984 ERROR cloudbaseinit.init File "c:\program files\cloudbase solutions\cloudbase-init\python\lib\site-packages\cloudbaseinit\plugins\windows\winrmcertificateauth.py", line 92, in execute 2017-02-07 09:07:56.750 1984 ERROR cloudbaseinit.init certdata, storename=x509.STORENAMEROOT) 2017-02-07 09:07:56.750 1984 ERROR cloudbaseinit.init File "c:\program files\cloudbase solutions\cloudbase-init\python\lib\site-packages\cloudbaseinit\utils\windows\x509.py", line 236, in importcert 2017-02-07 09:07:56.750 1984 ERROR cloudbaseinit.init raise cryptoapi.CryptoAPIException() 2017-02-07 09:07:56.750 1984 ERROR cloudbaseinit.init cloudbaseinit.utils.windows.cryptoapi.CryptoAPIException: CryptoAPI error: 0xd Appreciate any pointers on what the root cause of the error might be. Thanks, -- Kiran Cloudbase-init configuration: Sample pem cert: |