FAQ
When you install floating licenses on the Floating server, Max activations field determines on how many servers you are able to install that same license on.
Floating server is designed to be deployed in a secure internal network (e.g. with VPN). Therefore, each user should be a trusted user. If you still want to authenticate users, you can setup an authentication proxy for Floating server.
Floating server can be configured with multiple licenses at the same time. Setting the product allows us to determine to which product that license corresponds to.
I Configured Floating Server With One License. How Do I Add a Different License for the Same Product?
You are not able to add multiple licenses for the same product. If you want to change the license, you can remove the old license and add the new one.
Those keys only give you access to the License API, and not to the Management API. License API is a very limited subset of LicenseSpring API, so it is safe to share those keys.
Yes, the on-prem server can be run headless. After deployment using any of the available options, you can communicate with the server through command-line scripts. These scripts can be generated using our tool at LicenseSpring API Documentation. Every server functionality can be executed with corresponding command-line arguments.
When a license is activated through the on-prem server, the server uses the machine identifier of the operating system to generate a unique hardware ID, binding the license to that specific system. In Docker setups, the machine ID is derived from the host machine’s ID, and the license is tied to this hardware ID for future operations.
Is there a better implementation for node-locking in Docker setups on systems without internet access?
Yes, node-locking in Docker containers can be effectively implemented if the Docker volumes remain secure and unmodified. Our recommendation is to secure the Redis instance’s Docker volume, as it plays a key role in the node-locking mechanism. For systems without internet access, we provide offline or air-gapped licenses, which do not require internet connectivity. Alternatively, Physical Hardware Keys (dongles) can be used to enforce node-locking, requiring their presence for license validation.
No, currently, our floating server does not support detection of WSL (Windows Subsystem for Linux) instances.
The hardware ID is generated using the machine identifier from the underlying operating system or host machine. This unique ID is used to bind licenses to the system where the floating server is running.
How can I prevent server cloning when using the executable in air-gapped or virtualized deployments?
To protect against server cloning, the hardware ID is used to tie the server to a specific machine. LicenseSpring also supports Yubikey 5 hardware-based security for additional protection. If your environment doesn't allow external hardware (such as in fully virtualized systems), it's recommended to use expiration dates on licenses as an alternative safeguard. LicenseSpring is exploring software-only server cloning prevention protocols that may be available in the future.
Is the floating license server's database (Badger-DB) running as a separate process in the executable method?
No, the Badger-DB database is integrated directly into the floating server executable (floating-server.exe). There is no separate process to manage. The database runs within the executable, making it easier to monitor and control without extra overhead.
