Skip to content

Create an Imperva WAF machine

Create an Imperva WAF machine so Certificate Manager - SaaS can discover the certificates of the sites in your Imperva Cloud Web Application Firewall (WAF) account and provision custom certificates to them. There are two Imperva WAF machine types. One runs the connector in the cloud, and the other runs it on a VSatellite in your network.

Before you begin

  • The System Administrator, PKI Administrator, or Resource Owner role. If you have the Resource Owner role, you must own or belong to at least one team.
  • If you want the connector to run on a VSatellite, an active VSatellite that can reach the Imperva API host and the domains of your sites on port 443.
  • An Imperva Cloud WAF account with at least one site.
  • An Imperva API ID and API Key that can list the sites in the account and upload custom certificates to them. When you create an API key in your Imperva account, Imperva also generates its API ID.

To create an Imperva WAF machine

  1. Sign in to Certificate Manager - SaaS.
  2. Click Installations > Machines.
  3. Click New, and then select Imperva WAF. To run the connector on a VSatellite, select Imperva WAF (VSatellite) instead.
  4. On the Properties step, in Name, enter a name for the machine.
  5. For Owning Team, choose the team that owns the machine. System Administrators and PKI Administrators can choose any team. Resource Owners can choose only a team they own or belong to.
  6. If you chose Imperva WAF (VSatellite), for VSatellite, choose a VSatellite that can reach the Imperva API. A VSatellite that's the primary of a high availability group shows its number of active replicas, and Certificate Manager - SaaS can run the machine's operations on any healthy VSatellite in the group.
  7. (Optional) In Hostname or IP Address, replace the default, my.imperva.com, only if you reach the Imperva API at a different host. This is the host of the Imperva API, not the address of one of your sites. If you leave it empty, Certificate Manager - SaaS uses my.imperva.com.
  8. (Optional) In Port, replace the default, 443, if you reach the Imperva API on a different port.
  9. For Credential Type, choose how to provide the credentials:

    • Enter Credentials to enter the credentials in the next step. This is the default.
    • Select Credentials to use shared credentials from a credential manager integration. Then, for Credential, choose the credential.

    Note

    Select Credentials requires the credential manager capability, which requires additional licensing. Without it, Credential shows No credentials are available. System Administrators and PKI Administrators can choose any credential. Resource Owners can choose only the credentials that belong to their teams.

  10. If you chose Enter Credentials, in API ID and API Key, enter your Imperva API ID and API Key. If you chose Select Credentials, the stored credential must hold the API ID as its username and the API Key as its password.

    Note

    Certificate Manager - SaaS encrypts the credentials you enter and doesn't display them again. On the machine's Properties tab, they appear masked. To keep a stored credential when you edit the machine, leave its masked value unchanged. Keep your own secure record of the credentials in case you need them again.

  11. (Optional) To have the connector write a detailed log for troubleshooting, select Enable Debug logging. It's disabled by default. The log hides the API Key and other secrets.

  12. Click Test Access. After the connection succeeds, click Continue. The Discovery step opens.

    Note

    A successful test confirms that Imperva accepts the API ID and API Key and that the account has at least one site. It doesn't check whether the API key can upload certificates.

  13. (Optional) To skip certificates that have already expired, enable Exclude Expired Certificates.

    Discovery finds every site the API key can access, and then connects to each site's domain on port 443 to read the certificate the site presents. A site whose domain doesn't respond isn't discovered. If the account has no sites, discovery fails.

  14. (Optional) To discover certificates on a schedule, enable Schedule. For Repeat every, choose Day, Week, or Month, and then in At, enter the time. For Week, select the days of the week. For Month, enter the days in Day of month. Times are in Coordinated Universal Time (UTC).

  15. Click Continue. The Provisioning step opens.
  16. (Optional) To provision certificates on a schedule, enable Schedule. For Repeat every, choose Day, Week, or Month, and then in At, enter the time. For Week, select the days of the week. For Month, enter the days in Day of month. Times are in Coordinated Universal Time (UTC).

    Scheduled provisioning pushes only certificates that are queued for deployment, such as renewed certificates, so renewals install during the window you choose.

  17. Click Finish.

What's next?

After you create the machine, provision a certificate to it. You can also run discovery on the machine at any time to track the certificates of your Imperva sites.