What is the best practice to protect licenseKey

[shakiem_saunders]

Is there a suggested best practice for protecting the licenseKey for handsontable from prying eyes.

Right now a licensed handsontable instance is instantiated like

new Handsontable(container, {
licenseKey: ‘XXXXX-XXXXX-XXXXX-XXXXX-XXXXX’,
stretchH: “all”,
…
});

Nothing is really preventing prying eyes from inspecting the page viewing the license-key and gaining free access to a pro version on handsontable.

[aleksandra_budnik]

Hi @shakiem_saunders

we do not have any special system to hide the key.

It has to be in the initialization settings so you cannot share it via updateSettings somewhere in the code. I assume that if one wants to steal a license any system (in the JS world) can’t block it.

[shakiem_saunders]

Okay, thanks!

[aleksandra_budnik]

You’re welcome.

I am here if you would have any additional questions.