Describe the bug
When a signed key pair is exported as PKCS#12 and attempted to be installed on a Windows Server 2016 it will not go past the 'password' screen. Neither a blank password nor one set during export works. I have tested this on 2 different Windows Server 2016 servers, and the exported file works fine in Windows Server 2019. Using v5.4.2 I was able to create the certificate, export it, and install it on the Windows Server 2016 server without issue.
To Reproduce
Steps to reproduce the behavior:
Export Key Pair in KSE
Save file
Attempt to install it on a Windows Server 2016 to the Local Machine Store location
See error
Expected behavior
The password to be accepted whether it is blank or is set during export.
Screenshots
Environment
Version of KSE: 5.5.1
Version of Java: 17.0.1
Client Platform (OS): Windows 10 21H1 19043.1526
Server Platform (OS): Windows Server 2016 Standard 10.0.14393
Describe the bug When a signed key pair is exported as PKCS#12 and attempted to be installed on a Windows Server 2016 it will not go past the 'password' screen. Neither a blank password nor one set during export works. I have tested this on 2 different Windows Server 2016 servers, and the exported file works fine in Windows Server 2019. Using v5.4.2 I was able to create the certificate, export it, and install it on the Windows Server 2016 server without issue.
To Reproduce Steps to reproduce the behavior:
Expected behavior The password to be accepted whether it is blank or is set during export.
Screenshots
Environment