Non-Licensed Product

A license expires when the end of the term for that license has passed. A corrupted license is not valid. For details about expired licenses, refer to Expired License. For more about corrupted licenses, refer to Corrupted (Invalid) License.

Warning: From 10.0.x onwards, the protectors will display the following behaviour with regards to the ESA licensing -

An expired or invalid license will block policy, key, and deployment services on the ESA and via the DevOps APIs. An existing protector will continue to perform security operations. However, if you add a new protector or restart an existing protector, then the protector will not receive any policy until a valid license is applied. In addition, you will not be able to perform any other task from the Policy Management UI unless you obtain a valid license. On performing any action on the Policy Management UI, you will automatically be navigated to the License Manager screen as shown in the following screenshot.

For more information about obtaining a valid license, refer to Obtaining a Validated License.

License Expiration Notification

If the expiry of your license is less than or equal to 90 days, then the License Information dialog box appears when you log in to the ESA.

This dialog box specifies the number of days by when your license is going to expire. Click Acknowledge to continue accessing the ESA Web UI.

On the ESA Web UI, a message in the Notification pane reminds you that your license is due to expire. This reminder message appears every day from one month prior to the expiration date.

Expired License

A license expires depending on the expiration time and date settings in the license file. In the Notification pane of the ESA Web UI, Expired license status is displayed.

Corrupted (Invalid) License

If a license has been corrupted, in the Licenses pane of the ESA Web UI, then the Invalid license status is displayed.

If a license has been corrupted, in the Licenses pane of the ESA Web UI, then the Invalid license status is displayed.

A license may be corrupted in the following cases:

• License file has been changed manually.
• License file has been deleted.
• System date and time has been modified prior to when the license was applied to the product.

CAUTION: You MUST NOT change the system date and time to an earlier date and time than the license has been generated. This can lead to the license deactivation. The daylight saving time change is done automatically.

CAUTION: You MUST NOT edit or delete the license file saved on ESA since it can lead to license deactivation.

License Alerts

The Hub Controller generates warning logs at start-up, and once per day, when a license is about to expire, has expired, or is invalid. The ESA Web UI and Policy Management generate alert notifications about license status.

Once the system detects that the current system date is less than or equal to 30 days from the expiration date, an audit event is generated. For a temporary license, the system generates alerts once the ESA is installed.

Once the license is expired or becomes invalid, the Data Security Platform produces logs and notifications. These logs and notifications informs you about the change in the state of the license. You can refer to the Alerts and Notifications when License at Risk table for more details.

The Expiration Date field shows notifications about the current license status. In that field it will show the number of days left before the license expires.

You can also set up separate email notification alerts when licenses are about to expire using the ESA Web UI. For more information about setting up separate email notification alerts, refer to the Enterprise Security Administrator Guide.

The following table lists the system notifications and alerts about the status of the license at risk.

Table - Alerts and Notifications when License at Risk

• ←Previous
• Next→