ForgeRock Identity Platform 7.5

Prepare the servers

This is not a comprehensive platform implementation guide. These sample setup instructions show a minimal integration of platform components to get you started.

The ForgeRock Identity Platform offers maximum extensibility and flexibility in self-managed deployments. The platform includes many features and options these sample setup instructions do not cover. If you don’t need maximum extensibility and flexibility, there are simpler alternatives:

  • To consume the platform as a service, use ForgeRock Identity Cloud.

  • To deploy in Kubernetes, start with the ForgeOps reference implementation.

For help with your deployment and to validate your plans before deploying in production, contact ForgeRock.

Downloads

The sample deployments use software from the ForgeRock Download Center and other locations.

Download the required files for your sample deployment:

Component Downloads

AM

AM-7.5.0.zip

Amster-7.5.0.zip

apache-tomcat-9.0.52.zip1

DS

DS-7.5.0.zip

IDM

IDM-7.5.0.zip

mysql-8.0.29-macos12-x86_64.tar.gz2

mysql-connector-java-8.0.29.zip2

IG

IG-2024.3.0.zip

Platform UI3

PlatformUI-7.5.*.zip

1 Download this from the Apache site; ForgeRock does not ship Apache software.

2 Separate identity stores deployment only. Download these from the MySQL site; ForgeRock does not ship MySQL software.

3 (Optional) The alternative is to pull the Platform IU Docker images.

Basic requirements

These basic evaluation requirements concern the sample deployments.

Before deploying the platform in production, make sure the deployment meets all the requirements for each server component product. For details, refer to the release notes for each product.

Memory and disk space

These are basic sizing requirements for each sample deployment:

  • Reserve 1 GB RAM for each server product you install.

  • Reserve at least 10 GB disk space for the files.

  • For DS, reserve 5% + 1 GB of the filesystem size as free disk space.

Production deployments may have very different requirements.

Operating systems

Common supported operating systems for the server component products include:

  • Microsoft Windows Server

  • Red Hat Enterprise Linux and Rocky Linux

  • Ubuntu Linux

For details, refer to the release notes for each product.

Although it is not a supported operating system for the platform, you can try the sample deployments on Apple macOS.

Java

Supported Java versions for the sample deployments include:

  • Java 17.0.8 or later

Before installing the servers, set the JAVA_HOME environment variable.

Keep your Java installation up-to-date with the latest security fixes. Some security features may require later updates.

For details, refer to the release notes for each product.

Hosts and ports

The sample deployments use these hostnames and port numbers:

Component Hostname Port numbers

AM

am.example.com

HTTP: 8081

DS

directory.example.com

Admin: 4444

LDAP: 1389

LDAPS: 1636

IDM

openidm.example.com

HTTP: 8080

HTTPS: 8443

IG

platform.example.com

HTTP: 9080

HTTPS: 9443

Platform Admin UI

admin.example.com

HTTP: 8082

Platform End User UI

enduser.example.com

HTTP: 8888

Platform Login UI

login.example.com

HTTP: 8083

Sample deployment on a single computer

The sample deployments assume all servers are deployed on their own hosts.

To try a sample deployment on a single computer, the recommended alternative is to use the ForgeOps Cloud Developer’s Kit (CDK) on Minikube.

If you nevertheless choose to demonstrate these sample deployments on your computer, add aliases for the fully qualified domain names used for the servers and platform UIs to your /etc/hosts file:

127.0.0.1    admin.example.com
127.0.0.1    am.example.com
127.0.0.1    directory.example.com
127.0.0.1    enduser.example.com
127.0.0.1    login.example.com
127.0.0.1    openidm.example.com
127.0.0.1    platform.example.com

Next step

Copyright © 2010-2024 ForgeRock, all rights reserved.