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>
This commit is contained in:
parent
8fb9df01db
commit
546ffd7dcf
|
|
@ -15,10 +15,5 @@
|
||||||
<parameterName>ExternalCredential</parameterName>
|
<parameterName>ExternalCredential</parameterName>
|
||||||
<parameterType>Authentication</parameterType>
|
<parameterType>Authentication</parameterType>
|
||||||
</namedCredentialParameters>
|
</namedCredentialParameters>
|
||||||
<namedCredentialParameters>
|
|
||||||
<certificate>DocusignJWT</certificate>
|
|
||||||
<parameterName>ClientCertificate</parameterName>
|
|
||||||
<parameterType>ClientCertificate</parameterType>
|
|
||||||
</namedCredentialParameters>
|
|
||||||
<namedCredentialType>SecuredEndpoint</namedCredentialType>
|
<namedCredentialType>SecuredEndpoint</namedCredentialType>
|
||||||
</NamedCredential>
|
</NamedCredential>
|
||||||
|
|
|
||||||
Loading…
Reference in New Issue