Below you will find the various attributes for the entitlement resource. Entitlements
can be attached to policies and to licenses to grant named "permissions" for things
such as application features.
Entitlements can be attached to the following resources:
Policies: Any entitlement attached to a policy will automatically be attached to
all licenses which implement the given policy.
Licenses: Entitlements attached to a license are one-off and only apply to that
specific license resource.
Releases: Entitlements can be attached to releases through constraints,
in order to assert that a given licensee possesses the necessary entitlements
before being allowed to access a release's artifacts.
An authentication token with privileges to view the resources: either an admin, a product, a license which the entitlement is attached to (via license key or a license token), or a user which the entitlements is attached to.
Updates the specified entitlement resource by setting the values of the parameters
passed. Any parameters not provided will be left unchanged.
Renaming an entitlement code that is already in use may cause license validations
using the old entitlement code to fail. We suggest making sure the existing code
is no longer in use before changing it, to prevent unintended license validation
Returns a list of entitlements. The entitlements are returned sorted by creation date,
with the most recent entitlements appearing first. Resources are automatically
scoped to the authenticated bearer e.g. when authenticated as a license,
only entitlements attached to that specific license will be listed.
To list entitlements for an individual policy
or license, use the given resource's
scoped entitlements relationship.
An authentication token with privileges to view the resources: either an admin, a product, a license which the entitlements are attached to (via license key or a license token), or a user which the entitlements are attached to.