Creating a license rule
You create a license rule to specify for which users a login access rule is available. It is possible to have a login access rule without a license rule, but in that case, the login access rule is applied globally across the system, and that is not recommended.
Do the following:
-
Select License management on the QMC start page or from the StartS drop-down menu to display the overview.
-
Select Login access rules in the panel to the right.
-
Select a login access rule and click Edit.
To create a new login access rule, see: Creating login access rules .
-
Under Associated items, select License rules.
-
Click Create associated rule.
-
Edit the license rule as needed:
- Identification
- Basic
- Advanced
-
Optionally, edit the Advanced properties and create the Conditions for the rule.
-
Click Apply to create and save the license rule.
The license rule was successfully added to the associated items is displayed at the bottom of the page.
Disabled | Select to disable the rule. The rule is enabled by default. |
Name | The name of the login access rule. Mandatory. |
Description | Enter a description of the rule. |
Resource filter | If you change the resource filter, the rule may not work as intended. |
Operator | Descriptions and examples |
---|---|
= |
This operator is not case sensitive and returns True if the compared expressions are exactly equal. Example: user.name = ”a*” The user named exactly a* is targeted by the rule. |
like |
This operator is not case sensitive and returns True if the compared expressions are equal. Example: user.name like ”a*” All users with names beginning with an a are targeted by the rule. |
!= |
This operator is not case sensitive and returns True if the values in the compared expressions are not equal. Example: user.name != resource.name All resources that do not have the same name as the user are targeted by the rule. |
Conditions | Define the resource, user, or combined conditions that the rule should apply to. |
Did this page help you?
If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!