From 546ffd7dcffd1f746686a3202138f79434efb7ad Mon Sep 17 00:00:00 2001
From: paulh <paje0101+demo01@gmail.com>
Date: Thu, 9 Apr 2026 21:11:25 -0400
Subject: [PATCH] Remove erroneous ClientCertificate from CLMs1NamedCreds

JWT signing is handled by the DocusignJWT external credential. The
ClientCertificate parameter was adding unnecessary mTLS configuration
that DocuSign's API does not require. Now matches CLMuatNamedCreds.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
---
 .../CLMs1NamedCreds.namedCredential-meta.xml                 | 5 -----
 1 file changed, 5 deletions(-)

diff --git a/force-app/main/default/namedCredentials/CLMs1NamedCreds.namedCredential-meta.xml b/force-app/main/default/namedCredentials/CLMs1NamedCreds.namedCredential-meta.xml
index 80d4811..195ffba 100644
--- a/force-app/main/default/namedCredentials/CLMs1NamedCreds.namedCredential-meta.xml
+++ b/force-app/main/default/namedCredentials/CLMs1NamedCreds.namedCredential-meta.xml
@@ -15,10 +15,5 @@
         <parameterName>ExternalCredential</parameterName>
         <parameterType>Authentication</parameterType>
     </namedCredentialParameters>
-    <namedCredentialParameters>
-        <certificate>DocusignJWT</certificate>
-        <parameterName>ClientCertificate</parameterName>
-        <parameterType>ClientCertificate</parameterType>
-    </namedCredentialParameters>
     <namedCredentialType>SecuredEndpoint</namedCredentialType>
 </NamedCredential>