https://docs.protegrity.com/10.1/docs/lg/Recent content in Protegrity Data Security Platform Licensing onHugoenhttps://docs.protegrity.com/10.1/docs/lg/lg_obtaining_a_validated_license/Mon, 01 Jan 0001 00:00:00 +0000https://docs.protegrity.com/10.1/docs/lg/lg_obtaining_a_validated_license/<p>You can validate the license from the <strong>Licenses</strong> pane, available in the ESA Web UI. You can refer to the following screenshot. Only a user with ESA Administrative permissions can request and activate the license.</p> <p><img src="https://docs.protegrity.com/10.1/docs/images/activate_license_screen.png" alt="Activate License Screen" title="Activate License Screen"></p> <h2 id="requesting_license">Requesting a License</h2> <p>You can request a validated ESA license while your temporary license is valid, or invalid, or has already expired.</p> <p>To request an ESA license:</p> <ol> <li> <p>As an ESA administrator, proceed to <strong>Settings</strong> &gt; <strong>Licenses</strong>.</p>https://docs.protegrity.com/10.1/docs/lg/lg_nonlicensed_product/Mon, 01 Jan 0001 00:00:00 +0000https://docs.protegrity.com/10.1/docs/lg/lg_nonlicensed_product/<p>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 <a href="https://docs.protegrity.com/10.1/docs/lg/lg_nonlicensed_product/#expired_license">Expired License</a>. For more about corrupted licenses, refer to <a href="https://docs.protegrity.com/10.1/docs/lg/lg_nonlicensed_product/#corrupted_license">Corrupted (Invalid) License</a>.</p> <p><strong>Warning:</strong> From 10.0.0 onwards, the protectors will display the following behaviour with regards to the ESA licensing -</p> <p>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. <strong>In addition, you will not be able to perform any other task from the Policy Management UI unless you obtain a valid license.</strong> On performing any action on the Policy Management UI, you will automatically be navigated to the <strong>License Manager</strong> screen as shown in the following screenshot.</p>https://docs.protegrity.com/10.1/docs/lg/lg_cluster_licensing/Mon, 01 Jan 0001 00:00:00 +0000https://docs.protegrity.com/10.1/docs/lg/lg_cluster_licensing/<p>There are two types of restrictions that can be applied to your Protegrity license. A Configuration Lock is not machine specific and therefore can be used on other nodes in a cluster. A Node Lock is specific to the machine address of the node, and therefore cannot be used on other nodes. Node Lock is the stronger of the two restrictions and it will always take precedence when applied.</p> <p>The descriptions of these restrictions follow:</p>