Container

Installation guidance for running Fortified ID Access on Container.

Access is distributed as a Docker image. This page covers running a basic instance, mounting customer configuration, and using available startup options in container environments.

Prerequisites

Docker installed on the host.
Access credentials to the Fortified ID image registry (fortifiedid.jfrog.io).

Pull the image

docker pull fortifiedid.jfrog.io/docker/fortifiedid/integrity-access:<version>

Replace <version> with the target release.

Run the container

The minimal command to start a single node:

docker run -p 8080:8080 --detach --name integrity \
  fortifiedid.jfrog.io/docker/fortifiedid/integrity-access:<version> \
  -c Node config/config.json

Argument	Description
`-c`	Route all output to stdout. Omit to write logs to a file inside the container instead.
`Node`	Start the Node module.
`config/config.json`	Configuration file path, relative to `SERVER_HOME` inside the container.

Mount custom configuration

The image ships with a minimal stub configuration. Mount your own customer directory to provide configuration, modules, and other runtime files:

docker run -p 8080:8080 --detach --name integrity \
  -v /path/to/customer:/opt/fortifiedid/servers/integrity-server/customer \
  fortifiedid.jfrog.io/docker/fortifiedid/integrity-access:<version> \
  -c Node customer/config/config.json

Environment variables

Variable	Default	Description
`SERVER_LOG_LEVEL`	`INFO`	Log verbosity: `TRACE`, `DEBUG`, `INFO`, `WARN`, or `ERROR`.
`SERVER_LOG_APPENDER`	`File`	Log destination: `File` or `Console`. Passing `-c` at startup sets this to `Console`.
`SERVER_LOG_DIR`	`<SERVER_HOME>/logs`	Directory for log files when using file logging.
`SERVER_HOME`	`.`	Server home directory inside the container. Resolved from the working directory at startup.
`JAVA_HOME`	—	Path to the JRE to use. Defaults to `java` on `PATH`.
`JVM_CONFIG`	—	Comma-separated list of JVM configuration profiles to activate (see below).

JVM configuration profiles

Pass one or more profile names via JVM_CONFIG to activate optional JVM settings:

Profile	Description
`customer`	Loads customer-specific JVM options from `bin/customer/java.config`, for example `-Dcustomer_home=customer` and customer-specific Log4j configuration.
`read-only`	Starts the server in read-only mode.
`jmx`	Enables JMX metrics configuration.
`jmx_remote`	Enables remote JMX startup options.
`prometheus`	Enables Prometheus metrics configuration.

Example - customer config in read-only mode:

docker run -p 8080:8080 --detach --name integrity \
  -e JVM_CONFIG=customer,read-only \
  -e SERVER_LOG_LEVEL=TRACE \
  -v /path/to/customer:/opt/fortifiedid/servers/integrity-server/customer \
  fortifiedid.jfrog.io/docker/fortifiedid/integrity-access:<version> \
  -c Node customer/config/config.json

When the customer profile is enabled, Access loads JVM options from:

/opt/fortifiedid/servers/integrity-server/bin/customer/java.config

This can be used to expose customer-specific system properties such as:

-Dlog4j.configurationFile=customer/config/log4j2.xml
-Dcustomer_home=customer

This makes properties like ${system.customer_home} available in container deployments in the same way as in other installation types.

Verify installation

Check the log to confirm the server bootstrapped successfully:

docker logs -f integrity

Then open a browser and navigate to:

http://localhost:8080

A welcome page confirms the service is running.