Skip to content
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Install OpenIAM from RPM

Install the full OpenIAM stack on a single Linux VM with the RPM installer.

Goal: the full OpenIAM stack installed and initialized on the Linux host. Time: 60–90 minutes, much of it waiting on downloads and service startup. Prerequisites: Prepare your lab complete; RPM downloaded and checksum-verified in /usr/src.

Before you start: two things the installer will do to you

1

Install the package

cd /usr/src
sudo rpm -i openiam-2026.11.2.noarch.x86_64.rpm

Use the OpenIAM version you chose, the version number above is used as the example only.

This unpacks the stack to /usr/local/openiam, installs the openiam-cli command, creates the openiam OS user, raises file-descriptor limits — and schedules the reboot. Let the machine reboot, then log back in.

2

Run the initializer

sudo openiam-cli init

Everything is logged to /usr/local/openiam/init.log. The prompts, in order:

Prompt
Answer for this guide

Environment type

1 (Non-Production / Dev — 80 GB disk, 48 GB RAM minimums are enforced here)

Does this box have Internet access?

y

Database to install

1 for the MariaDB golden path (see below for PostgreSQL)

mariadb-secure-installation

Runs interactively: set a root password, remove anonymous users, disallow remote root, remove the test DB, reload privileges. Record the root password

Enable TLS for Redis?

n for the POC

Database/Flyway section

See step 3

Install OpenIAM reverse proxy module?

y — this installs Apache httpd + mod_openiam and opens ports 80/443 in firewalld

Install Prometheus+Grafana monitoring?

y (optional but cheap; Grafana on :3000, default admin/admin)

The initializer downloads the dependency repo, backend and frontend binaries, and the LDAP connector for your OS release (it detects el9 from /etc/os-release), then initializes Vault, Cassandra/JanusGraph, OpenSearch, RabbitMQ, and Redis before the database section.

3

Database section (Flyway)

The installer asks for the nine OpenIAM schema names (accept defaults: openiam, activiti, groovy, auditlog, batchtasks, pbac, certification, privacy, reporting), the database type, host and port, and whether to initialize the schema and users.

MariaDB (golden path): database type mysql, host localhost, port 3306, answer y to "initialize OpenIAM Schema and Users", and supply the root password from step 2. Schema creation runs automatically. Review the validation summary and confirm with y.

PostgreSQL (variant): choose 2 at the database prompt and the installer installs PostgreSQL 18.4 on this host, asking you to set a password for the postgres user — or answer 3 and provision your own server first, reachable from this host, with a superuser. Then: database type postgres, your host and port (5432), y to initialize. For PostgreSQL the installer writes the init SQL to /tmp/init.sql and asks you to run it manually against your server:

psql -h <pg-host> -U postgres -f /tmp/init.sql
rm /tmp/init.sql   # it contains secrets — remove it after initialization

Re-run init after the schema exists (a failed database stage does not mark the host initialized, so init runs again cleanly). The installer also asks whether the database is a managed service like AWS RDS — those need log_bin_trust_function_creators = 1 set on the instance; answer y there if so.

4

First start

At the end, init enables the systemd timers, starts the stack, and configures nginx. First startup takes 10–15 minutes — services come up in dependency order.

One architecture note so later pages make sense: there are two web layers. Apache httpd with mod_openiam (installed by the reverse-proxy step) is the public entry point on ports 80/443; behind it, an internal nginx on port 8080 fronts the individual UI applications. You configure certificates on Apache (next page); you never touch nginx directly.

openiam-cli status        # per-service health
openiam-cli log           # follow the startup log (Ctrl-C to stop)
curl -k -I -L http://127.0.0.1/idp/login   # expect HTTP 200 when the stack is up

Useful commands from here on: openiam-cli start | stop | status | log [service].

If it failed

Symptom
Likely cause

Init exits immediately citing RAM/disk

VM below 48 GB RAM / 80 GB free on / — resize, re-run openiam-cli init

Init exits citing swap

swapoff -a and remove swap from /etc/fstab, re-run

Downloads fail

No route to download.openiam.com — fix egress or use the offline installation guide

openiam-cli start says not initialized

Init didn't complete — check /usr/local/openiam/init.log for the failing stage

Services stuck starting

Check infra.status gating and per-service logs in /usr/local/openiam/logs/

Starting over (uninstall / reset)

A failed init can simply be re-run (see the top of this page). Use this reset when init completed but you want different answers — or when you just want a guaranteed-clean slate:

sudo openiam-cli stop
sudo rpm -e openiam
sudo rm -rf /usr/local/openiam          # data and config are NOT removed by rpm -e
sudo userdel -r openiam 2>/dev/null

If you installed MariaDB locally and want a truly clean slate, also remove it and its data (yum remove mariadb-server && rm -rf /var/lib/mysql), and remove /etc/httpd/conf.d/mod_openiam*.conf if the proxy was installed. On a lab VM the fastest reset of all is a hypervisor snapshot taken right before rpm -i — take one now if you haven't.

You know this worked when…

Last updated

Was this helpful?