System Requirements

Please take note of the system requirements for the eperi sEcure Platform (see Administrator Manual) and additionally the following requirements regarding the eperi sEcure Salesforce.

DNS Requirements

In order to set up the eperi sEcure Platform, a registered DNS domain is required.

For the example below, the registered domain is crm.example.com.

The DNS should be resolvable both internally and externally.

It is recommended to use a wildcard DNS for this domain, e.g.:

A Record

crm.example.com --> 1.2.3.4 (server IP address)

CNAME Record

*.crm.example.com --> crm.example.com

CNAME Record

*.liveagent.crm.example.com --> crm.example.com

MX Record

crm.example.com --> crm.example.com

If wildcard is not allowed, then at a minimum the following DNS records should be created to resolve to the eperi sEcure Platform server's IP address:

  • crm.example.com
  • salesforce.crm.example.com
  • force.crm.example.com
  • content.crm.example.com
  • login.crm.example.com
  • auth.crm.example.com
  • mstmassemail.crm.example.com
  • visual.crm.example.com
  • <ssoSubdomain>.crm.example.com (if you plan to configure Single Sign-On for your Salesforce org)

Please be aware that the Omnichannel/Liveagent feature requires the wildcard subdomain in order to work.

SSL Certificate Requirements

A PKI SSL certificate is required for the reverse proxy, to ensure that all communication between the end user and the eperi sEcure Platform are fully encrypted.

A wildcard certificate from a public CA would be preferred. Alternatively you could use a certificate signed by your internal Certificate Authority, where the CA Cert is generally trusted by your standard desktops / browsers. The use of a self-signed certificate is possible, but not recommended, as it requires additional steps to avoid certificate errors.

The eperi sEcure Platform requires a trusted SSL certificate with (as a minimum) the domain name as subject (e.g. crm.example.com) and the following subject alternative names:

  • crm.example.com
  • salesforce.crm.example.com
  • force.crm.example.com
  • content.crm.example.com
  • login.crm.example.com
  • auth.crm.example.com
  • mstmassemail.crm.example.com
  • visual.crm.example.com
  • *.liveagent.crm.example.com
  • <ssoSubdomain>.crm.example.com (if you plan to configure Single Sign-On for your Salesforce org)

For the setup and installation of the eperi sEcure Platform, you will need to obtain:

  • the private key
  • the certificate
  • the certificate chain including root and intermediate CA certificates

This should be created as a PKCS #12 key store, for the import via the eperi sEcure Platform Admin Console.

Secure Salesforce Access

The eperi sEcure Platform uses the Salesforce API and needs secure access to Salesforce.

Therefore the following are required:

  • A Salesforce administrator user for setting up the Salesforce environment.
  • A connected app configured for use by the Gateway. This can be set up by eperi once administrative access is given.

Salesforce End User Permissions

Salesforce End Users which access Salesforce via the eperi sEcure Platform additionally need the administrative permission API Enabled. The permission can be set in Salesforce in a user profile or in a permission set.

API Request Limit

For search functions and the use of reports, the eperi sEcure Platform uses API Requests with an API User. Please be sure, that you have an API request limit that is big enough for your users.

Note: There is no package installed into Salesforce, as this is not required. The eperi sEcure Platform simply leverages the Salesforce API’s.