Cloud Licensing Permissions
The Cloud Licensing Permissions page enables you to set default usage permissions for CL keys. This is relevant only for service-hosted cloud licensing and is used in conjunction with Accounts.
You can set cloud licensing permissions at the following levels:
>Global level (defined on this page). Provides the default cloud licensing permissions for all customers and accounts.
>Customer level. Customers inherit the default, global cloud licensing permissions when an entitlement is activated using Produce and Push. You can modify these permissions for specific customers as needed. For details, see Customers.
> Account level. Each account inherits the default cloud licensing permissions defined for the associated customer. You can modify these permissions for specific accounts as needed. For details, see Accounts.
To define the default, global cloud licensing permissions:
1.From the navigation pane, select Configuration > Cloud Licensing Permissions to view the Cloud Licensing Permissions page.
2.Fill in the customer permissions for service-hosted cloud licensing (described in the next section) and click Save.
Customer Permissions for Service-Hosted Cloud Licensing
The following table describes the default cloud licensing permissions for customers.
| Attribute | Description |
|---|---|
| Maximum Number of Accounts |
The maximum number of accounts that can be defined Possible values: >Unlimited (default) >Number of Network Seats |
| Maximum Number of Registered Machines |
A client machine may be automatically registered with the account when a protected application runs for the first time. Possible values: >1-10. The maximum number of remote machines that are allowed to use this account to access the license server machine. Each machine is automatically registered the first time it accesses the license server machine. When the maximum number of machines are registered, no additional machines can use the account. >Unlimited. An unlimited number of remote machines are allowed to use the account to access the license server machine. The machines are not registered. Default: 5 |
| Waiting Period for Reusing Deleted or Disabled Registered Machines (Days) |
The waiting period represents the number of days that the administrator contact must wait before changing the status of a machine that they disabled or deleted using the Sentinel EMS customer portal. This is relevant only after the first time that the registration status changes. The purpose of this setting is to discourage administrator contacts from performing unauthorized license sharing. How does the waiting period work? Suppose the Sentinel EMS vendor administrator created an account profile for Alex, who is an administrator contact. The first time that Alex runs an application that uses a CL key, his laptop is automatically registered to his account profile. Both the vendor administrator and Alex can see this registration in the Registered Machines tab under the record for Alex's profile on the Accounts page in Sentinel EMS. One day, Alex decides to give his license to his friend, Joan. Alex uses the self-service customer portal to delete or disable the machine where the protected application ran (his laptop). Joan, pretending to be Alex, runs the protected application from her machine. After two days, Joan tells Alex that she doesn't want to use the application anymore. So, Alex opens the customer portal and disables or deletes the machine that was automatically registered when Joan ran the application (Joan's laptop). Since Joan is no longer using the application, Alex decides to run the application on his laptop again, but only two days have elapsed. Since the Waiting Period for Reusing Deleted or Disabled Auto-Registered Machines is set to the default seven days, Alex must now wait for five more days before he can run the application on his laptop. Possible values: >1-30 (An integer representing 1-30 days) >No waiting period. Select the Allow Immediate Reuse check box to override the waiting period and allow deleted or disabled machines to be automatically re-registered immediately. Default: 7 |
| Allow Online Connection to Licenses |
Enables a remote machine with an installed identity string to consume a license from the service-hosted, cloud license manager server. Possible values: Yes or No |
| Allow License Detaching |
(Relevant for both automatic and on-demand detaching) Enables a client machine to detach a license (a network seat) for a protected application from the service-hosted, cloud license manager server whenever a license is required. >Automatic detaching. Detached licenses are deducted from the pool of available networks seats on the CL key. The client machine retains the license up to the number of hours specified even if the connection to the license server is interrupted. This enables the protected application to continue to operate without connection to the license server machine. When the detached license expires, it automatically returns to the pool of network seats on the CL key and is disabled on the machine. Maximum offline duration: 2 hours >On-demand detaching. End users can access a manually detached license from a CL key for a specified number of days. This is useful if they want to work with a protected application and expect to be disconnected from the company’s network for an extended period. On-demand detaching works only in offline mode. To use a manually detached license: On the machine where the CL key is located, an administrator can generate an H2R file that contains a detached license. The administrator transfers the file to the recipient (for example, the end user) who then applies the H2R file on the machine. Maximum duration: 14 days Possible values: Yes or No |
| Allow Concurrency for Detached Licenses |
(Relevant only for on-demand detaching and visible only if Allow License Detaching is set to Yes) Enables a machine with the identity string to detach one or more network seats with concurrency from the license server machine. These seats can then be accessed concurrently on the machine that receives the detached license. A detached license with concurrency can be used to: >Set up second-level license servers. These can be used to provide greater control over the distribution of network seats within an organization and to minimize the overhead of license administration. For more information, see the Sentinel LDK Software Protection and Licensing Guide. >Control the number of local hardware resources used by an application. For example, a protected application can be limited to use 4 out 8 CPUs. This requires a detached license with 4 seats, where access to each CPU is granted after the application logs in to the license. In this example, the fifth login will be denied, ensuring that only 4 CPUs are in use. Possible values: Yes or No |