Migration information—using Lime 3.4.4 with pre 3.4.9 clients

When Lime main server 3.4.4 is used together with Lime Java SDK 3.4.9, license expiry will be set to 23:59:59 UTC on the day of expiry, both in locally stored license data and in the main servers database.

If the server is updated to 3.4.4 but the client is not updated to 3.4.9, local license expiry will not be at 23:59:59, it will be at the time of day for license activation. On the server, the time of day may or may not be 23:59:59 depending on when the license was created/modified.

Main server expiry is created when the license is created or modified. Existing licenses will not get the 23:59:59 UTC time of day when the server is updated to 3.4.4, until the license is modified (using the main server manager).

Local expiry is created when the license is activated. A license must be deactivated and then activated again (with version 3.4.9) to get the 23:59:59 time of day.

License validation will first check the current time against the locally stored expiry time, and then check expiry with the main server. Both checks must pass for validation to pass.

Example 1: Existing activated license, main server updated to 3.4.4
The old local and main server expiry times remain.

Example 2: Existing license, main server updated to 3.4.4, license activated with client older than 3.4.9
The license already has expiry on the main server (the old way based on time of day at license creation/modifcation). Locally, expiry will be calculated the old way (based on time of activation). Same local and main server expiry times as in Example 1.

Example 3: Main server updated to 3.4.4, new/modified license, license activated with client older than 3.4.9
License expiry on the main server will be 23:59:59 UTC on the expiry day. Local license expiry will be based on time of activation. The result is that local and server expiry will not match each other. Validation will fail at the earlier of the two expiry times.