v2.1.6+Configuring the agent-level HTTP policy for Inline Scripting tasks

Use the agent configuration properties to set the default outbound HTTP policy for all Inline Scripting tasks that run on an agent, controlling which hosts scripts are permitted to reach.

Before you begin

To configure the agent-level HTTP policy, you must have administrator access to the agent configuration file.

About this task

Inline Scripting tasks apply the following precedence when determining the HTTP policy for outbound calls:

  1. Task-level parameters (if explicitly set in the task definition)
  2. Connection profile values (if a connection is assigned to the task)
  3. Agent-level properties (set in the agent configuration file or as Quarkus properties)
  4. Built-in defaults (all outbound fetches blocked)

The agent-level properties set in this procedure apply as defaults to all Inline Scripting tasks running on the agent that do not have a connection or task-level override configured.

Procedure

  1. Open the agent configuration file on the agent host.

    For the location and format of the agent configuration file, see Setting up an environment for the tasks run by HCL UnO agent.

  2. Set the HTTP policy and execution limit properties in the agent configuration file or as Quarkus properties.

    Properties can be set using a dedicated properties file or as Quarkus properties with the uno.tasktype.scripting prefix (for example, uno.tasktype.scripting.javascript.allowedHosts=...). Each property can be set in one of two forms:

    • language.property — applies the value to a specific language runtime only (where language is javascript or python).
    • property — applies the value to all language runtimes.
    Property Default Description
    allowedHosts Not set Comma-separated list of host or domain patterns that scripts are permitted to reach. When set, all hosts not on the list are denied. When neither allowedHosts nor blockedHosts is set at any level, all outbound fetches are blocked.
    blockedHosts Not set Comma-separated list of host or domain patterns that are always denied, regardless of the allowedHosts list.
    scriptTimeoutSeconds 60 Default script run timeout in seconds. Range: 1–600.
    memoryLimitMb 256 Default memory ceiling in MB. Range: 64–1024.
    fetchTimeoutSeconds 30 Default per-request HTTP timeout in seconds.

    The following example sets an allowlist for JavaScript only and a common script timeout for all languages:

    javascript.allowedHosts=api.internal.example.com,data.internal.example.com
scriptTimeoutSeconds=120
  3. Save the configuration file and restart the agent for the changes to take effect.

Results

Inline Scripting tasks running on this agent without a task-level or connection-level HTTP policy override use the values you configured as their default outbound HTTP policy.

What to do next

To override the agent-level policy for a specific task, configure a connection on that task definition. For details, see Inline Scripting task parameters and output properties.