Imperva

This section will guide you to overcome the various issues faced by you during the use of Imperva WAF and its various functionalities.

Issues in Communicating to Imperva

Error Message Possible Cause Possible Solution
Communication to <ip> has failed

Invalid credentials

Imperva WAF is down.

Please check if the correct Imperva credentials are provided.

Please login to the SecureSphere console to check if Imperva is running.
Connection timeout

Internet / Proxy connection is not provided from AppViewX node.

Firewall settings blocking the REST API request

 Login to AppViewX portal and provide proxy details in Menu->Settings->General->Proxy and Check Firewall settings

Issues in Config Fetch

Error Message Possible Cause Possible Solution
Communication to <ip> has failed

Invalid credentials

Imperva WAF is down.

Please check if a correct Imperva credentials are provided

Please login to the SecureSphere to check if Imperva is running.
Device has 0 sites. No sites configured in Imperva. Please login to the SecureSphere to check if Sites are configured.
Device has 0 Server Group No Server Groups configured in Imperva. Please login to the SecureSphere to check if Server Groups are configured.
Device has 0 Services No Services configured in Imperva Please login to the SecureSphere to check if Services are configured.

Issues in Certificate Discovery

Error Message Possible Cause Possible Solution
Please provide information as required

  1. Discovery name is not given or length is less than 2 characters.

  2. Interval between batches info. is missing when execution type is sequential.

  1. Enter a valid name with a minimum of 2 characters.

  2. Provide a time interval between batches in minutes.
Please select a devices No WAF account is selected in the “Discover By” section. Select at least one device to discover certificates from.
Discovery Status Failed

Check if internet /Proxy connection is provided in AppViewX node.

 Login to AppViewX portal and provide proxy details in Menu->Settings->General->Proxy.
No Certificates discovered from Imperva WAF SSL Certificates are not discovered from Imperva due to API restrictions. Imperva Rest API doesn't allow the public Certificate String in the API responses. Only Certificate attributes like common name, signature, Expiry date and Issuer details are captured.

Check with AppViewX PM team / SME for more details

Issue in Push and Rollback

Error Message Possible Cause Possible Solution
An item with this name already exists - please select a different name SSLKeyName should be unique. Kindly ensure to provide a unique name in “Certificate File Name” field on Connector page.
Site not found Unable to find the site to push the certificate Please login to SecureSphere to check if the Site is available.
Server Group not found Unable to find the Server Group to push the certificate Please login to SecureSphere to check if the Server Group is available.
Services not found Unable to find the Service to push the certificate Please login to SecureSphere to check if the Service is available.