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
Copy file name to clipboardExpand all lines: CHANGELOG.md
+7-4Lines changed: 7 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,6 +5,8 @@
5
5
* .NET6 assemblies are no longer supported.
6
6
* Fixed a problem when passing a bad CSP, the job was reporting successful, but did not actually add/bind the certificate.
7
7
* Enhanced Crypto Service Provider (CSP) discovery and validation to work correctly on localized Windows installations. Customers running Traditional Chinese Windows (zh-TW / CP950) reported that certificate add jobs were failing with "Crypto Service Provider ... is either invalid or not found on this system." even when the requested CSP was installed. The root cause was that `Get-CryptoProviders` parsed `certutil -csplist` output and matched on the literal English label "Provider Name:", which is translated on non en-US Windows, causing the enumerated provider list to come back empty and every CSP name to fail validation. Provider enumeration now reads from the culture-invariant registry hive `HKLM:\SOFTWARE\Microsoft\Cryptography\Defaults\Provider` (with a code-page-safe `certutil` fallback for hardened systems where the registry hive is unavailable), and CSP name matching in `Validate-CryptoProvider` now uses ordinal, case-insensitive comparison so results are unaffected by the current thread culture (Turkish-I folding, full-/half-width character folding, etc.).
8
+
* Since adding JEA, lower privileged users can now run the extension in a local PowerShell Runspace without needing to be a member of the Administrators group. This is a security improvement, but it does require that the user has been granted access to the JEA endpoint on the target server. When running IIS jobs without JEA endpoints, the credentials entered will still need Administrative permissions. If you are running into permission issues, please check your JEA configuration and ensure that the user has been granted access to the endpoint.
9
+
* Fixed IIS Inventory error propagation across all connection types (Local, WinRM, JEA, SSH). Previously, when the cmdlet encountered errors (e.g., insufficient admin rights), it used Write-Warning/Write-Information which didn't signal failure to the orchestrator. Over remote sessions, PS.HadErrors remained false and jobs returned 0 certificates with no indication of failure, making it impossible to distinguish between "no certificates found" vs "access denied". The cmdlet now returns structured KeyfactorResult JSON objects for all error scenarios, which the orchestrator detects and reports in JobResult.FailureMessage. This ensures reliable error detection and reporting regardless of connection type (Local PowerShell, WinRM HTTP/HTTPS, JEA endpoints, SSH sessions).
8
10
9
11
3.0.2
10
12
@@ -23,26 +25,27 @@
23
25
* Fixed the SNI/SSL flag being returned during inventory, now returns extended SSL flags
24
26
* Fixed the SNI/SSL flag when binding the certificate to allow for extended SSL flags
25
27
* Added SSL Flag validation to make sure the bit flag is correct. These are the valid bit flags for the version of Windows:
26
-
### Windows Server 2012 R2 / Windows 8.1 and earlier (IIS 8.5)
28
+
### Windows Server 2012 R2 / Windows 8.1 and earlier (IIS 8.5)
0 commit comments