Using LexActivator with Ruby
First of all, login to your Cryptlex account and download the LexActivator library for Windows, macOS, or Linux:
The above download package contains the library which you will be using to add licensing to your app.
Adding licensing to your app
After you've added a product for your app in the admin portal, you will need to do the following things:
Note the product id for the product (from the actions menu in the table).
Download the Product.dat for the product (from the actions menu in the table).
Download the example project from Github.
Product.dat contains product data that is used by LexActivator. Product id is the identifier of your product that is to be used in the code.
Adding the library to your app
LexActivator example project for Ruby contains LexActivator.rb and LexStatusCodes.rb files. You will need to add these files to your Ruby project. It contains all the LexActivator API functions needed to add licensing to your app. Depending on the OS you are targeting you need to copy the respective LexActivator.dll, libLexActivator.so, or libLexActivator.dylib to your project.
LexActivator has a dependency on VS2015
runtime on Windows. On the target machines where you will deploy your app, you can install the VS2015
runtime, if not present, using the link: https://www.microsoft.com/en-in/download/details.aspx?id=48145
Setting product.dat file and product Id
The first thing you need to do is either embed the Product.dat file in your app using SetProductData()
function or set the absolute path of the file using SetProductFile()
function.
The next thing you need to do is to set the product id of your application in your code using SetProductId()
function. It sets the id of the product you will be adding licensing to.
If your app requires admin (root) privileges to run (e.g. services, daemons etc.), instead of passing PermissionFlags::LA_USER
flag, you need to pass PermissionFlags::LA_SYSTEM
flag.
In case your app doesn't have write access to the disk, you can use PermissionFlags::LA_IN_MEMORY
flag instead, which causes all the data to be stored in the memory. But this would require you to activate the license every time you restart the app.
License activation
To activate the license in your app using the license key, you will use ActivateLicense()
LexActivator API function. It invokes the /v3/activations
Cryptlex Web API endpoint, verifies the encrypted and digitally signed response to validate the license.
The above code should be executed at the time of license activation.
Verifying license activation
Each time, your app starts, you need to verify whether your license is already activated or not. This verification should occur locally by verifying the cryptographic digital signature of activation. Ideally, it should also asynchronously contact Cryptlex servers to validate and sync the license activation periodically. For this, you need to use IsLicenseGenuine()
LexActivator API function.
The above code should be executed every time user starts the app. After verifying locally, it schedules a periodic server check in a separate thread.
Need more help
In case you need more help with adding LexActivator to your app, we'll be glad to help you make the integration. You can either post your questions on our support forum or can contact us through email.
Last updated