From db13d8c0015ef3362627ef493682bb66278a45c6 Mon Sep 17 00:00:00 2001 From: Hossein Shafagh Date: Fri, 5 Feb 2021 11:51:30 -0800 Subject: [PATCH] documentation --- docs/administration.rst | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/docs/administration.rst b/docs/administration.rst index f150296b..3f282369 100644 --- a/docs/administration.rst +++ b/docs/administration.rst @@ -959,10 +959,16 @@ The following parameters have to be set in the configuration files. If there is a config variable ENTRUST_PRODUCT_ take the value as cert product name else default to "STANDARD_SSL". Refer to the API documentation for valid products names. -.. data:: ENTRUST_CROSS_SIGNED_RSA +.. data:: ENTRUST_CROSS_SIGNED_RSA_L1K :noindex: - This is optional. Entrust provides support for cross-signed subCAS. One can set ENTRUST_CROSS_SIGNED_RSA to the respective cross-signed subCA PEM, such as L1K, Lemur will replace the retrieved subCA with ENTRUST_CROSS_SIGNED_RSA. + This is optional. Entrust provides support for cross-signed subCAS. One can set ENTRUST_CROSS_SIGNED_RSA_L1K to the respective cross-signed RSA-based subCA PEM and Lemur will replace the retrieved subCA with ENTRUST_CROSS_SIGNED_RSA_L1K. + + +.. data:: ENTRUST_CROSS_SIGNED_ECC_L1F + :noindex: + + This is optional. Entrust provides support for cross-signed subCAS. One can set ENTRUST_CROSS_SIGNED_ECC_L1F to the respective cross-signed EC-based subCA PEM and Lemur will replace the retrieved subCA with ENTRUST_CROSS_SIGNED_ECC_L1F. .. data:: ENTRUST_USE_DEFAULT_CLIENT_ID