Metadata API Developer Guide
j
No Results
Search Tips:
- Please consider misspellings
- Try different search keywords
InboundCertificate
File Suffix and Directory Location
InboundCertificate components have the suffix .inboundCertificate and are stored in the inboundCertificates folder.
Special Access Rules
InboundCertificate is available when the MutualAuthentication permission is enabled in your org.
Version
InboundCertificate components are available in API version 49.0 and later.
Fields
This metadata type contains the following fields:
| Field Name | Field Type | Description |
|---|---|---|
| expirationDate | date | Required. The date on which the certificate expires. |
| issuer | string | Required. The certificate’s issuer. |
| masterLabel | string | Required. A friendly name that you create for the certificate. Limited to 64 characters. |
| serialId | string | Required. The serial number for the certificate. |
Declarative Metadata Sample Definition
The following is an example of an InboundCertificate component.
<InboundCertificate xmlns="http://soap.sforce.com/2006/04/metadata">
<expirationDate>2021-02-04</expirationDate>
<issuer>C=USA,ST=CA,L=San Francisco,O=Salesforce.com,OU=00Dxx0000006Jm7,CN=newTestCert</issuer>
<masterLabel>TestMutualAuthCert2</masterLabel>
<serialId>29161320252531323757470546071624</serialId>
</InboundCertificate>The following is an example package.xml that
references the previous
definition.
<?xml version="1.0" encoding="UTF-8"?>
<Package xmlns="http://soap.sforce.com/2006/04/metadata">
<types>
<members>*</members>
<name>InboundCertificate</name>
</types>
<version>49.0</version>
</Package>Usage
To prevent simple impersonation from compromising security, you can require clients and servers to prove their identity to each other with a mutual authentication certificate.