Dependencies between fields returned by /app/rest/server/licensingData

Hello Kamil,

Here is the logic behind each field:

• valid - the key is well-formed and readable (it may be expired or obsolete at the same time, though);
• active - the key is actually used by the server (I believe that, for example, if you have two up-to-date server licenses at the same time only one will be actively used by TeamCity);
• expired - the key has expired (this applies to time-limited keys like evaluation licenses);
• obsolete - the key's maintenance period does not include the major version release date for the currently installed version of TeamCity;
• maintenanceEndDate - used in conjunction with obsolete boolean field, shows the maintenance period end date
• expirationDate - used in conjunction with expired boolean field, shows when the time-limited license expires

Usually, a license may be used indefinitely with the version that it covers, so in the majority of cases you may want to check the obsolete and maintenanceEndDate field values.

Please let me know if this helps.

Hi Fedor,

Thank you for quick answer!

So let me understand correctly:

• valid - will be false if either "expired" or "obsolete" will be true
• expired - will be true once current date will be later than expirationDate
• obsolete - will be true once TC major version release date will be after "maintenanceEndDate"

Do I understand it correctly?

Additional question here, is "TC major version release date" is the same value as in "serverEffectiveReleaseDate"?

Hello Kamil,

valid is not exactly correct - it will return true as long as license is readable. For example, IZAEF-889Z0-0TXDV... might be a valid license, but I-AM-DEFINITELY-NOT-A-LICENSE... is not.

In regards to serverEffectiveReleaseDate - yes, exactly, this is the date we compare maintenanceEndDate with.

Oh ok, to sum up use case, so if I want to check if license is working and available, I have to check if it's:

1. "expired" to false

2. "obsolete" on false,

3. and "valid" on true.

If either of those are changed to different value, means license is not working correctly (so f.e. for agent license, additional agent will not be added + additional build configurations limit will not be increased with this license).