Proper use of SetCustomDeviceFingerprint


I was drive testing the python api and stumbled on this call where technicallly we can
LexActivator.SetCustomDeviceFingerprint therefore changing the default device fingerprint.

In the document, it mentions that we should call this right after setting the product data we get from the web portal in the product itself but when calling the custom fingerprint the function throws an invalid product data error 42.

When i remove the call the license activates without the custom fingerprint.

I am running this on a RedHat 8 system.

What am I missing …

Best regards

Please upgrade to 3.23.4 if you are using the cryptlex python module. That solved the issue I have been having.


can be a good pattern as documented in the api.