From 5358826a0c26db75cec60fd11bf4957945b8100a Mon Sep 17 00:00:00 2001
From: Guy Sheffer <144031599+guyshe-jfrog@users.noreply.github.com>
Date: Mon, 20 Jan 2025 12:50:03 +0200
Subject: [PATCH] Update docs to include JAS binary requirements (#179)

---
 .../authentication.md                                           | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/jfrog-applications/jfrog-cli/binaries-management-with-jfrog-artifactory/authentication.md b/jfrog-applications/jfrog-cli/binaries-management-with-jfrog-artifactory/authentication.md
index 61175e9..1c776fc 100644
--- a/jfrog-applications/jfrog-cli/binaries-management-with-jfrog-artifactory/authentication.md
+++ b/jfrog-applications/jfrog-cli/binaries-management-with-jfrog-artifactory/authentication.md
@@ -76,6 +76,6 @@ In this case, you'll need to make those certificates available for JFrog CLI, by
 
 **Note**
 
-1. The supported certificate format is PEM.
+1. The supported certificate format is PEM. Make sure to have ONE file with the ending .pem. OR provide as many as you want and run the c_rehash command on the folder as follows  :`c_rehash ~/.jfrog/security/certs/`.
 2. Some commands support the **--insecure-tls** option, which skips the TLS certificates verification.
 3. Before version 1.37.0, JFrog CLI expected the certificates to be located directly under the **security** directory. JFrog CLI will automatically move the certificates to the new directory when installing version 1.37.0 or above. Downgrading back to an older version requires replacing the configuration directory manually. You'll find a backup if the old configuration under **.jfrog/backup**