User Restrictions for the Detach Operation

User Restrictions specified using Admin Control Center or Admin API are also applied when a user attempts to detach a license to be applied to a user’s machine.

Requests to detach a license from a license server are handled differently when they are issued using Admin Control Center on a remote machine and when they are issued using Sentinel Licensing API or Sentinel Admin API.

A request to detach a license issued using Sentinel Licensing API or Sentinel Admin API is evaluated based on user restrictions in the same manner as a request to consume a license.

However, a request to detach a license using Admin Control Center on a remote machine is evaluated differently. Admin Control Center on the remote machine does not pass the username to the license server machine. Therefore, user restrictions that are based on user name are applied differently, as described below:

>“allow” user restrictions that are based on a specific user name are not applied because the user name is not available to the License Manager on the license server. If a different restriction such as deny=all@all is also specified, the detach request will be denied.

>If any “deny” user restriction that is applicable for the request in all respects other than username exists, that restriction is applied even if the user name specified in the restriction does not match. For example: If the detach request was sent from a machine with the hostname host123, and a user restriction has been specified deny=skr@host123 on the license server machine, the detach request is denied even the user requesting the detach has a different username.