License File Diagram
The license file model represents the traditional approach to software licensing, where a digitally signed license file is distributed to customers and validated locally by the application without requiring communication with a licensing server. This model is ideal for scenarios where customers may operate in completely offline environments or when you prefer a simpler deployment model without the infrastructure requirements of server-based licensing.
The license file process works as follows:
The software developer creates a license template in the Babel Licensing Service.
The developer generates a license file based on the template, digitally signing it with a private key.
The Babel Licensing Service returns the generated license file.
The developer distributes the license file to the customer through their preferred delivery method (download, email, physical media, etc.).
The customer installs the license file in the appropriate location (typically the application directory).
When the application starts, it loads the license file from its location.
The application validates the license file's digital signature using an embedded public key.
The application verifies the license details, including expiration date, licensed features, and any restrictions.
If the license is valid, the application enables the appropriate features as specified in the license.
If the license is invalid (expired, tampered with, or otherwise not meeting requirements), the application displays an error message.
The application periodically revalidates the license during operation, but this validation occurs entirely locally without requiring any server communication.
Unlike activation and floating licenses, the file-based approach does not consume license tokens and operates independently of the Babel Licensing Service after the initial license generation. The license validation occurs entirely within the client application using the embedded public key to verify the license's authenticity and integrity.
The primary advantages of the license file model include simplicity, complete offline operation, and lower infrastructure requirements. However, this approach provides less visibility into license usage and fewer options for remote license management compared to the token-based licensing models.
Last updated