From 4e830a72ec683f7b64d80a63a7ca8334b8b14480 Mon Sep 17 00:00:00 2001 From: Lee Fine Date: Thu, 23 Jan 2025 18:19:43 +0000 Subject: [PATCH] ab#55979 --- docsource/rfpem.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docsource/rfpem.md b/docsource/rfpem.md index 0641a5d..128cffb 100644 --- a/docsource/rfpem.md +++ b/docsource/rfpem.md @@ -9,4 +9,4 @@ Use cases supported: 4. Single certificate stores with private key in an external file. 5. Single certificate stores with certificate chain in the file and private key in an external file -NOTE: PEM stores may only have one private key (internal or external) associated with the store, as only one certificate/chain/private key combination can be stored in a PEM store supported by RFPEM. Private keys will be stored in encrypted or unencrypted PKCS#8 format (BEGIN [ENCRYPTED] PRIVATE KEY) based on the Store Password set on the Keyfactor Command Certificate Store unless managing a PEM store that currently contains a private key in PKCS#1 format (BEGIN RSA PRIVATE KEY). Store password MUST be set to "No Password" if managing a store with a PKCS#1 private key. +NOTE: PEM stores may only have one private key (internal or external) associated with the store, as only one certificate/chain/private key combination can be stored in a PEM store supported by RFPEM. Private keys will be stored in encrypted or unencrypted PKCS#8 format (BEGIN [ENCRYPTED] PRIVATE KEY) based on the Store Password set on the Keyfactor Command Certificate Store unless managing a PEM store that currently contains a private key in PKCS#1 format (BEGIN RSA PRIVATE KEY or BEGIN EC PRIVATE KEY). Store password MUST be set to "No Password" if managing a store with a PKCS#1 private key, as encrypted PKCS#1 keys are not supported with this integration.