fix: support 403 allowlist (#595)

* fix: support 403 allowlist * chore: update config path for sf
salesforcecli · Sep 18, 2023 · 78d474e · 78d474e
1 parent b871b56
commit 78d474e
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/README.md b/README.md
@@ -10,7 +10,7 @@ We always recommend using the latest version of these commands bundled with the
 
 ### Allowlisting
 
-If a plugin needs to be installed in a unattended fashion as is the case with automation. The plugin acceptance prompt can be avoided by placing the plugin name in \$HOME/.config/sfdx/unsignedPluginAllowList.json
+If a plugin needs to be installed in a unattended fashion as is the case with automation. The plugin acceptance prompt can be avoided by placing the plugin name in \$HOME/.config/sf/unsignedPluginAllowList.json
 
 ```json
 [

diff --git a/src/shared/installationVerification.ts b/src/shared/installationVerification.ts
@@ -467,7 +467,7 @@ export async function doInstallationCodeSigningVerification(
     verificationConfig.log(`Successfully validated digital signature for ${plugin.plugin}.`);
   } catch (err) {
     if (err instanceof Error) {
-      if (err.name === 'NotSigned') {
+      if (err.name === 'NotSigned' || err.message === 'Response code 403 (Forbidden)') {
         if (!verificationConfig.verifier) {
           throw new Error('VerificationConfig.verifier is not set.');
         }
-Original file line number
+Diff line change
@@ Expand Up @@
     ### Allowlisting
-    If a plugin needs to be installed in a unattended fashion as is the case with automation. The plugin acceptance prompt can be avoided by placing the plugin name in \$HOME/.config/sfdx/unsignedPluginAllowList.json
+    If a plugin needs to be installed in a unattended fashion as is the case with automation. The plugin acceptance prompt can be avoided by placing the plugin name in \$HOME/.config/sf/unsignedPluginAllowList.json
     ```json
     [
@@ Expand Down @@