Note: This release is in preview. Features described here don’t become generally available until the latest general availability date that Salesforce announces for this release. Before then, and where features are noted as beta, pilot, or developer preview, we can’t guarantee general availability within any particular time frame or at all. Make your purchase decisions only on the basis of generally available products and features.

InboundCertificate

Represents a mutual authentication certificate that is imported to your Salesforce org.

Where possible, we changed noninclusive terms to align with our company value of Equality. We maintained certain terms to avoid any effect on customer implementations.

Important

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.

1<InboundCertificate xmlns="http://soap.sforce.com/2006/04/metadata">
2    <expirationDate>2021-02-04</expirationDate>
3    <issuer>C=USA,ST=CA,L=San Francisco,O=Salesforce.com,OU=00Dxx0000006Jm7,CN=newTestCert</issuer>
4    <masterLabel>TestMutualAuthCert2</masterLabel>
5    <serialId>29161320252531323757470546071624</serialId>
6</InboundCertificate>

The following is an example package.xml that references the previous definition.

1<?xml version="1.0" encoding="UTF-8"?>
2<Package xmlns="http://soap.sforce.com/2006/04/metadata">
3    <types>
4        <members>*</members>
5        <name>InboundCertificate</name>
6    </types>
7    <version>49.0</version>
8</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.

Metadata API Developer Guide