Before You Start

Autonomous Identity server software requires the following hardware and software requirements to run in your production environment. Autonomous Identity’s flexible architecture runs in a variety of network environments: on-prem, cloud, multi-cloud, and hybrid.

Files to Download

You deploy Autonomous Identity using a Docker image that pulls other dependent images from the ForgeRock Google Cloud Registry (gcr.io) repository and installs the components on a target node. ForgeRock Autonomous Identity customers must contact ForgeRock for a registry key to download the images. For specific instructions on obtaining the registry key, see How To Configure Service Credentials (Push Auth, Docker) in Backstage.

Autonomous Identity requires the following Docker image for installation.

Table 1: Autonomous Identity Software
Docker Image Docker Image URL

gcr.io/forgerock-autoid/deployer:2021.3.0

When you run the install process, you will download the image file from the ForgeRock Google Cloud Repository. For more information, see Install Autonomous Identity.

Hardware and Memory Requirements

Autonomous Identity has a number of components that include application, data, and analytics servers, which are all included in the Docker images. The minimum hardware and memory requirements for a single-node deployment are as follows:

Table 2: Hardware and Memory Requirements
Vendor Versions

Single Node Deployment

32 GB RAM, 8 CPU

Storage Requirements

Autonomous Identity has a number of components that include application, data, and analytics servers, which are all included in the Docker images. The minimum storage requirements for a single-node deployment are as follows:

Autonomous Identity requires the following minimum storage requirements:

Table 3: Storage Requirements
Type Size

Data Storage

100 GB (minimum), 1 TB (production)

Operating Systems Requirements

Autonomous Identity is supported on the following operating system:

Table 4: Operating System Requirements
Vendor Versions

CentOS

7.7 and higher

Java Requirements

Autonomous Identity software supports the following Java environments:

Table 5: Java Requirements
Vendor Versions

OpenJDK

8u262 and higher

Third Party Software Requirements

Autonomous Identity deployments uses the following third-party software:

Table 6: Third-Party Software Requirements
Component Version Usage

Python

3.6 and higher

Scripts

Docker CE

18.09.1

Container cluster management

Apache Cassandra

3.11.2 and higher

Database for all Autonomous Identity services

Apache Spark

3.1 and higher

Cluster to run Autonomous Identity analytics

Apache Livy

0.8.0-incubating and higher

REST interface to Spark master to run Autonomous Identity analytics

Mongo DB

4.4

Database for all Autonomous Identity services

HashiCorp Consul

1.7 and higher

Service discovery and configuration server

nginx

1.18 and higher

Reverse proxy for routing HTTPS traffic

Open Distro for Elasticsearch

1.9 and higher

Distributed, open source search engine for all data types.

OpenLDAP

2.4.50 and higher

An LDAP server backend.

Supported Browsers

The following browser is supported for use in production:

Table 7: Supported Browsers
Vendor Versions

Google Chrome

version 85.0.4183.121 and higher

Mozilla Firefox

version 86.0.1 and higher

Autonomous Identity Ports

The following ports are implemented in Autonomous Identity:

Table 8: Autonomous Identity Ports
Port Protocol Machine Description

2376

TCP

Docker

Secure Docker client communication. This port is required for the Docker machine, which orchestrates the Docker hosts.

2377

TCP

Docker

Communication between the nodes of a Docker swarm cluster. Only needed on manager nodes.

7946

TCP/UDP

Docker

Communication among nodes for container network discovery.

4789

TCP

Docker

Overlay network traffic.

7001

TCP

Cassandra

Internode communication.

9042

TCP

Cassandra

CQL native transport.

27017

TCP

MongoDB

Default ports for mongod and mongos instances.

5601

TCP

Open Distro for Elasticsearch

Port to access Kibana.

7077

TCP

Spark

Spark master internode communication port.

8998

TCP

Apache Livy

Apache Livy communication port.

40040-40045

TCP

Analytics

Spark driver ports for Spark workers to callback.

443

TCP

Autonomous Identity

Port to access the dashboard and API.

5601

TCP

Autonomous Identity

Port to Kibana.