certstore feature with windows credential manager

test/configs/certs/tlsauth/certstore/delete-cert-from-store.ps1

@@ -0,0 +1,2 @@
+$issuer="Synadia Communications Inc."
+Get-ChildItem Cert:\CurrentUser\My | Where-Object {$_.Issuer -match $issuer} | Remove-Item

test/configs/certs/tlsauth/certstore/import-p12-client.ps1

@@ -0,0 +1,5 @@
+$fileLocale = $PSScriptRoot + "\client.p12"
+$Pass = ConvertTo-SecureString -String 's3cr3t' -Force -AsPlainText
+$User = "whatever"
+$Cred = New-Object -TypeName "System.Management.Automation.PSCredential" -ArgumentList $User, $Pass
+Import-PfxCertificate -FilePath $filelocale -CertStoreLocation Cert:\CurrentUser\My -Password $Cred.Password

test/configs/certs/tlsauth/certstore/import-p12-server.ps1

@@ -0,0 +1,5 @@
+$fileLocale = $PSScriptRoot + "\server.p12"
+$Pass = ConvertTo-SecureString -String 's3cr3t' -Force -AsPlainText
+$User = "whatever"
+$Cred = New-Object -TypeName "System.Management.Automation.PSCredential" -ArgumentList $User, $Pass
+Import-PfxCertificate -FilePath $filelocale -CertStoreLocation Cert:\CurrentUser\My -Password $Cred.Password

test/configs/certs/tlsauth/certstore/pkcs12.md

@@ -0,0 +1,22 @@
+# PKCS12 Files
+
+Refresh PKCS12 files when test certificates and keys (PEM files) are refreshed (e.g. expiry workflow)
+
+- `client.p12` is a p12/pfx packaging of `client.pem` and `client-key.pem`
+
+`openssl pkcs12 -export -inkey ./client-key.pem -in ./client.pem -out client.p12`
+
+> Note: set the PKCS12 bundle password to `s3cr3t` as required by provisioning scripts
+
+## Cert Store Provisioning Scripts
+
+Windows cert store supports p12/pfx bundle for certificate-with-key import.  Windows cert store tests will execute 
+a Powershell script to import relevant PKCS12 bundle into the Windows store before the test. Equivalent to:
+
+`powershell.exe -command "& '..\test\configs\certs\tlsauth\certstore\import-<client,server>-p12.ps1'"`
+
+The `delete-cert-from-store.ps1` script deletes imported certificates from the Windows store (if present) that can
+cause side-effects and impact the validity of different use tests.
+
+> Note: Tests are configured for "current user" store context. Execute tests with appropriate Windows permissions
+> (e.g. as Admin) if adding tests with "local machine" store context specified.