You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Based on what I've research, the fix for this is to enable the private key exportable upon cert creation.
Since I am using the ACME-module and there's no way I can directly just append an enable command into my script does it mean I have to download the whole source code, update script then build.
After that import the module to the automation account?
The text was updated successfully, but these errors were encountered:
I'm a little bit irritated, that something like that would show up now.
There might be a change in a used command with .net 8 / PS 7.4, but the current version works well on my on-prem windows machines with PS 5.1.
If you have already patched the problem, you could open a PR and we'll take a look?
Hi, I have been working on SSL Automation on my Azure Account.
I have imported the ACME-PS module into my automation account.
ACME-PS PowerShell module
Version: 1.5.7
However, I have encountered the following:
�[91mExport-PfxCertificate: �[91mCannot export non-exportable private key.�[0m
Based on what I've research, the fix for this is to enable the private key exportable upon cert creation.
Since I am using the ACME-module and there's no way I can directly just append an enable command into my script does it mean I have to download the whole source code, update script then build.
After that import the module to the automation account?
The text was updated successfully, but these errors were encountered: