windows_certificates does nothing within Kitchen

[DanSibbernsen]

Cookbook versions

4.3.2, 3.1.0

Chef-client version

14.2.0, 12.19.36

Platform Details

Windows 10 (latest patches)
Windows Server 2016 (latest patches)
Created from Packer via JacqInTheBox

Scenario:

I run Kitchen converge with the following recipe:

windows_certificate "#{node['Certificates']['location']}/certificate.pfx" do
  pfx_password '*****'
  store_name node['Certificates']['TrustedFolder']
  action :create
end

.kitchen.yml from my windows cookbook:

driver:
  name: vagrant
  customize:
    cpus: 2
    memory: 4096

transport:
  name: winrm
  elevated: true

provisioner:
  name: chef_zero
  deprecations_as_errors: true

verifier:
  name: inspec

platforms:
  - name: windows_10
    driver:
       box: windows_10
       provider: parallels
  - name: windows_server_2016
    driver:
       box: windows_server_2016
       provider: parallels

Notably: if I pass in the wrong password, the recipe fails to converge. But if the password is correct, the recipe appears to succeed but no certificate is pushed into the TRUSTEDFOLDER.

Steps to Reproduce:

kitchen create; kitchen converge;

The issue started sometime between Summer of 2017 and Spring of 2018. I've got several working cases on outside environments, but Kitchen can't install my certificates or the certificates located in the Windows cookbook source. Nothing appears in the mmc.exe when I load up the Certificates snap-in (this is true for both "My user account" and "Computer account").

The next level of debugging would be into the ruby gem of win32-certstore, but I'm not sure how I would go about doing that via Kitchen.

Expected Result:

I expect the certificate to be installed and configured correctly.

Actual Result:

No certificate is created.

[piyushawasthi]

@DanSibbernsen This is occurred due to we have validation for certificate-store. Now we update the code in PR: chef/win32-certstore#36. Now if you open any store that not exist and want to add new certificate in that then our code will create new store for you and add new certificate in that.

[tas50]

This should be resolved in the latest version of the cookbook which uses and updated version of our win32-certstore gem. If you're still having this issue after updating the cookbook then please open this back up so we can dig in.