SLASCONE standard licenses have two expiration modes:
- Fixed expiration date
- Days after activation
ensuring compliance for the majority of licensing scenarios in production. However, for purposes of development, testing etc a temporary license needs to replace an existing (production) license. SLASCONE provides a very elegant way to create, activate and automatically deactivate temporary licenses.
The temporary mode is an edition (not a product or license) property. Typically, you create one edition allowing the temporary mode. Note that the temporary mode of an edition can not be changed. All licenses of a temporary edition, are temporary licenses.
There is no functional difference in terms of license parameters that can be defined, between normal and temporary licenses. In this context, a temporary license can have a fixed expiration date or an expiration date depending on the day of activation. However, in most cases temporary licenses have an n days after activation expiration mode.
A license's activation is based on a unique clientid. SLASCONE does not allow the simultaneous activation of two (not temporary) licenses with the same clientid. If you activate a license with a clientid, which is already activated with another license, the old license is automatically deactivated.
This is exactly where temporary licenses come into play: You can have two simultaneously activated licenses with the same clientid. However, the first has to be a not temporary and the second a temporary one.
During the time in which both licenses are active, the temporary has higher priority, controlling entitlements etc.
Once the temporary license expires, the not temporary takes control. Upon expiration of a temporary license, all of its tokens are unassigned.
There are no differences when dealing with temporary licenses: all relevant API functions such as activation, heartbeats etc function in the same way.