1.1 Prerequisites

You must have an Entrust CA Gateway configured for redirecting API calls between the client and the Entrust CA.

Refer to your Entrust CA Gateway documentation for recommendations of the hardware and software requirements and how to configure the gateway.

1.1.1 Supported Entrust CA Gateway versions

The Entrust CA Gateway may be integrated with multiple versions of Entrust Security Manager. Intercede expects that the certificate authority compatibility is managed by the Entrust CA Gateway and may differ from the versions Intercede has tested. You are recommended to test compatibility with MyID before deploying to production; support for certificate authorities that have not been tested by Intercede will be limited.

MyID has been tested with the following CA Gateway versions:

MyID has been tested with the following CA versions:

You can use Entrust certificates in the same way as any other certificates within MyID. You can issue certificates to cards or as soft certificates by specifying them in a credential profile.

Note: MyID has no specific requirements for Entrust Authority Security Manager (SM) or Entrust Security Manager Administration (SMA) – however, you must ensure that your Entrust system is installed and operational and available through the Gateway. See your Entrust documentation for details of additional requirements.

1.1.2 Certificate revocation list

The MyID application server must be able to communicate with the Certificate Revocation List (CRL) location. The CRL is checked for validity whenever MyID connects to the CA.