The following table describes the UI elements for this dialog box.
| Item | Description |
|---|---|
|
Script source code |
Shows the source code for the rule. You cannot edit the code in this field, so you must write your scripts in a text editor and then upload them. |
|
Script path |
Provides a space for you to type the path to a file containing the script code for the rule. Once you load the script into the authorization store, its source code will be displayed. |
|
Browse |
Opens the Browse dialog box so that you can browse to the file containing the script for the rule. |
|
Script type |
Specifies the scripting language used to create the rule. VBScript Specifies that the VBScript language is being used for the rule. For example, the following VBscript code always grants permission: AzBizRuleContext.BusinessRuleResult = True JScript Specifies that the JScript language is being used for the rule. For example, the following JScript always grants permission: AzBizRuleContext.BusinessRuleResult = true; |
|
Reload Rule into Store |
Reloads the rule into the store from the file provided in the Script path, and displays the source code. |
|
Clear Rule from Store |
Removes the rule from the store. |
Additional considerations
- When used to define members of an application
group, a script is called a business rule. When used to
define a role or task, a script is called an authorization
rule.
- The use of business rules and authorization
rules on each client computer is controlled by a registry setting.
In this version of Windows, rules are disabled by default. In
versions of Windows earlier than Windows Server 2008, they are
enabled by default. For more information, see Controlling
Authorization by Using Authorization Rules and Business
Rules.
- In addition, you can also disable rules
entirely for an authorization store on the Limits tab of the
authorization store properties sheet. For more information, see
Understanding
Authorization Manager Store Limits
Additional references