Trusted Storage License Models
Trusted storage models enable programmatic activation, that is, activation of license rights on a machine using a process that is completely hands-free and transparent to the user.
Trusted storage license models include these types:
| • | A retail activation license model is used in a retail scenario for activation of license rights in trusted storage on a standalone end-user machine. Unlimited instances of the licensed application can be run on that machine. You create a product that uses a retail activation model as one of the Client-Side Online Activation exercise prerequisites. |
| • | A floating transferable license model allows license rights to be written to the trusted storage of a license server. The license server can then transfer these rights to another server, or allow them to float over a network from which end users check them out. These license rights cannot be activated directly on end-user machines. |
| • | A floating borrowable license is first activated on a license server. It can be transferred to another license server, served as a floating license, or activated on an end-user machine for use when it is no longer connected to a license server. |
| • | An enterprise activation license model is used to activate license rights on an enterprise server, from which the license rights can be transferred to another server or activated on an end-user machine. These licenses cannot float over a network. You create a product that uses an enterprise activation model as one of the Server-Side Online Activation exercise prerequisites. |
License rights data in trusted storage is encrypted and authenticated to prevent tampering.
Transaction Keys
Products that use a trusted storage license model require at least one transaction key. A transaction key consists of a publisher ID, a set of transaction key seeds, binding, and anchors. Binding ensures that license rights held in trusted storage are not copied to another system, while anchors detect whether trusted storage has been tampered with, deleted, or restored.
A transaction key is linked with a product only if the product uses a trusted storage license model. The transaction key is linked with the product when the first trusted storage license model is linked with the product, and can be changed later or overridden. You must create at least one transaction key before linking a trusted storage license model with a product. Unlike license models, it is not necessary to deploy transaction keys.
You create a transaction key as one of the Client-Side Online Activation exercise prerequisites.