When importing a PFX or PEM file into the SBM Configurator, the error No Keypair entries found in the file is displayed. This means that the PFX or PEM does not have a public key, private key and complete chain of all certificate authorities responsible for signing the certificate .
SBM Configurator failed to recognize certificate with private key if the keystore contained duplicated certificates. For example if the JKS file there are two entries: one is a key entry with the whole chain, and second is a public certificate a copy of what is already present in the key chain. The error message will be:
If you ignore the warning and complete the import, the certificates are still successfully imported. Alternatively, you can import each certificate in the chain individually.
System cryptography: Use FIPS 140 compliant cryptographic algorithms, including encryption, hashing and signing algorithms Configurator shows this error: "not part of the Windows Platform FIPS validated cryptographic algorithms"
2. Open IIS Manager, and add a binding for https that uses the certificate. 3. Open Configurator 4. In the Component servers section, set the following:
If you import the certificate manually into IIS, you are presented with an option to make the certificate exportable. If you export the certificate manually into IIS first making it exportable and then import via Configuration IIS tab, you are presented with a warning that certificate already exists in the keystore. If you then ignore the warning and click on Apply within configurator to implement the changes.
