Scripted Actions - Account-Level Secure and Inherited Variables

Scripted Actions - Account-Level Secure and Inherited Variables

Nerdio Manager allows you to manage Account-level Secure and Inherited variables.

Secure Variables

Secure variables have the following features:

  • Stored in the Key Vault.

  • Can be passed to account-level scripted actions using the $SecureVars.Variable_Name variable name.

  • Only available for scripted actions.

Inherited Variables

Inherited variables have the following features:

  • Stored in the Nerdio Manager database.

  • Can be passed to account-level scripted actions, policies, and global apps using the $InheritedVars.Variable_Name variable name.

Tips:

  • This feature is especially helpful if you want to pass sensitive information to a scripted action without passing it via clear text.

  • See Scripted Actions - MSP-Level Secure and Inherited Variables for details about MSP-level variables.

  • Configuration drift ignores the account-level Inherited variables because you have intentionally created drift by defining different variables for each account.

To manage account-level secure and inherited variables:

  1. At the Account level, navigate to Settings Portal.

  2. In the Secure and Inherited variables for scripted actions tile, select the action (add, edit, or remove) you wish to perform.

  3. To add or edit a global secure variable, enter the following information:

    • Name: Type the name of the variable.

      Note: The variable name must be between 1 and 20 alphanumeric characters.

    • Value: Type the variable's value.

    • Policy type: Select the policy type.

    • Windows scripts: Optionally, from the drop-down list, select which Windows scripted action(s) the variable is passed to.

    • Azure runbooks: Optionally, from the drop-down list, select which Azure Runbook(s) the variable is passed to.

  4. When you have entered the desired information, select OK.

Was this article helpful?

1 out of 1 found this helpful
Have more questions? Submit a request

Comments (0 comments)

Article is closed for comments.