PSPKI module changes

[miclip]

It seems the latest PSPKI module has changed. New-SelfSignedCertificate is now New-SelfSignedCertificateEx

PSPKI Documentation for New-SelfSignedCertificateEx

[wangzq]

Is it a typo that the version should be 3.2.5 instead of 3.5.2?

[wangzq]

Also, current code seems only working with 3.2.5 exact version number, which may be a problem once the module is upgraded to a newer version such as 3.2.6:

if($PSPKIVersion.Major -ieq 3 -And $PspkiVersion.Minor -ieq 2 -And $PspkiVersion.Build -ieq 5) {

[ChackDan]

@wangzq -Good suggestion.
@miclip - thankyou for letting me know. I will update the package with your suggestions.

[aviade]

I fixed it and sent out a PR #31 @ChackDan - please review. Because of this bug the script is using New-SelfSignedCertificate instead of New-SelfSignedCertificateEx when using the latest (3.2.6) version of PSPKI.

The problem is that the New-SelfSignedCertificate code path creates a certificate that can't be used from SF cluster since the private key cannot be extracted

[aviade]

Fix is now merged.

[antonGritsenko]

Just for better understanding. Will selfsigned certificate generation work if PSKI module is not installed (with this "install cert to My store | Export it" approach)? I have issue with certificate generated by the Invoke-AddCertToKeyVault and just want to be sure what I'm, doing everything in correct way.