This guide is intended for Enterprise IT Administrators provisioning AARI Extensions within their organization.

Outbound hosts to allowlist from client devices:

Firewall, port, and protocol requirements for Automation Anywhere deployment: Automation 360 Ports, protocols, and firewall requirements

The PixieBrix Web Service makes API calls to the Control Room API for syncing permissions and AARI Extensions. If you’re running your Control Room behind a firewall (e.g. inside a VPC) then inbound traffic from the PixieBrix Web Service may be blocked and the integration will not function properly.

To fix this, you’ll need to allowlist incoming PixieBrix traffic in your firewall configuration. We provide a load-balanced pair of IP addresses so if one IP fails, traffic will automatically route through the second IP with health checks and automated failover. The PixieBrix static outbound IP addresses and ports are:

Once your Control Room is successfully configured, contact PixieBrix support (support@pixiebrix.com) to enable the static IP feature on your Control Room.

Officially, AARI Extensions support the latest two versions of the Chrome Web Browser.

Force install browser extension via Group Policy:

Enterprise Browser Extensions are configured using Chrome’s managed storage feature. For end-users, set the following extension properties:

Windows

On Windows, use the registry to set the properties for the extension:

By default, the Browser Extension does not have access to pages or to make network requests. During Authentication (see below), the Browser will prompt the user to grant permission for the Browser Extension to connect to the Control Room.

Additionally, when activating AARI Extensions that run on pages (e.g., Workday), the end-user will be prompted to grant the Browser Extension access to modify those pages.

To pre-allow access to the Control Room and any other pages. Add the URLs to the Runtime Allowed Hosts form the Browser Extension

Hosts to Include

See Use AuthConfig App to enable OAuth2 services in the Automation Anywhere documentation portal for how to set up Login with Automation Anywhere

To enable Login with Google, ensure the following Google Client is in the allowlist:

To enable Login with Microsoft, ensure the following Azure Application is in the allowlist:

Our Security and Compliance Overview and Privacy and Security Policies are available publicly.

Additional security information on the Chrome Browser Extension is available in the