Utilizing components, you can manage hardware components for machines. For
example, you could fingerprint and track hardware (and even non-hardware)
components such as CPU serial number, motherboard serial number, hard-drive
ID, GPU GUID, MAC address, or even non-hardware components such as
IP address.
This allows you to offer a more sophisticated fingerprinting strategy for
machines, where a certain percentage of these components must be valid
in order to pass license validation, configurable through the policy's
component matching strategy.
This can help reduce problems related to cloning, e.g. a series of machines
all have the same device GUID due to a misconfigured or erroneous cloning
procedure, by also checking hardware components in addition to the original
device GUID.
It can also reduce superfluous activations due to a more typical machine
fingerprint changing due to a machine's underlying hardware being
upgraded.
Below you will find the various attributes for the component resource, as well
as the component resource's relationships. Components can be used to track
and manage a machine's hardware components.
The unique fingerprint of the component, e.g. a motherboard serial number. This can be an arbitrary string, but must be unique within the scope of the machine it belongs to or according to the policy's component uniqueness strategy.
An authentication token with privileges to create the resource: either an admin, the product it belongs to, the license it belongs to (via license key or a license token), or the user it belongs to via the machine or license owner (unless the license is protected).
The unique fingerprint of the component, e.g. a motherboard serial number. This can be an arbitrary string, but must be unique within the scope of the machine it belongs to or according to the policy's component uniqueness strategy.
A 201 Created response will be returned along with the new component object.
Upon error, an errors object will be returned along with an
HTTP status code indicating the type of error. When an error occurs, the
data property will not be included.
An authentication token with privileges to view the resource: either an admin, a product which the owning machine belongs to, the license it belongs to (via license key or a license token), or the user it belongs to.
A 200 OK response will be returned along with a component object.
Upon error, an errors object will be returned along with an
HTTP status code indicating the type of error. When an error occurs, the
data property will not be included.
A 200 OK response will be returned along with the updated component object.
Upon error, an errors object will be returned along with an
HTTP status code indicating the type of error. When an error occurs, the
data property will not be included.
An authentication token with privileges to manage the resource: either an admin, the product it belongs to, the license it belongs to (via license key or a license token), or the user it belongs to via the machine or license owner (unless the license is protected).
Upon error, an errors object will be returned along with an
HTTP status code indicating the type of error. When an error occurs, the
data property will not be included.
Returns a list of components. The components are returned sorted by creation date,
with the most recent components appearing first. Resources are automatically
scoped to the authenticated bearer e.g. when authenticated as a user,
only components for that specific user will be listed.
An authentication token with privileges to view the resources: either an admin, a product which the owning license belongs to, the license which the components belong to (via license key or a license token), or the user which the components belong to.
A 200 OK response will be returned along with a list of component objects.
Upon error, an errors object will be returned along with an
HTTP status code indicating the type of error. When an error occurs, the
data property will not be included.