Migrating per-machine keys to floating licensing
A floating license pool looks like a server setting: "allow 25 concurrent users instead of 25 named machines." It is not. The machine-count model and the concurrent-seat model are two different conversations between the client and the service, and the clients that are already installed only know how to have one of them. Flip the server before the field is ready and you get the worst licensing bug…
A floating license pool operates differently than a machine-count model in that it does not assign named machines, but rather allows 25 concurrent users. The client and service negotiate using two different conversations, and existing installed clients only understand one of them. If the server is changed before the field is ready, it can result in a major licensing bug where paying customers are locked out while the dashboard still appears functional.
To avoid this issue, the transition from node-locked to floating licensing should be treated as a rolling protocol migration. Begin by shipping a dual-mode SDK that can read a per-key seat.model claim, and then start minting floating keys once the SDK reaches the field. The server reconciles each machine's old activation into the new pool atomically, ensuring the shared capacity remains intact throughout the migration.
The crucial decision of which model to use is made by the client, not the server, and should be included in each license. This allows both the server and the client to read the model before choosing a path. The first deliverable is an SDK that reads the claim and dispatches the correct action based on the seat model. Once the SDK is in place, the server will reconcile each machine's activation when it first claims a floating seat, preventing double-counting and ensuring the capacity cap is never exceeded.
This approach allows customers to upgrade at their own pace, with the model being embedded in each license and the SDK handling the transition smoothly.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.