Changes

The name of the IDM evaluation-only Docker image repository has been changed to gcr.io/forgerock-io/idm-cdk. This image repository was formerly named gcr.io/forgerock-io/idm.

The IDM canonical configuration for the CDK has been incorporated into the idm-cdk Docker image.

Because of this, you no longer need to copy files from the docker/idm/config-profiles/cdk directory when you initialize a new configuration profile. Simply create a new subdirectory under the docker/idm/config-profiles directory.

The new bin/ds-debug.sh script lets you obtain diagnostic information for any DS pod running in your cluster. It also lets you perform several cleanup and recovery operations on DS pods.

For more information, see Debug script.

The RCS Agent is no longer available in the CDM and CDK deployments.

Building your own rcs-agent Docker image is no longer required when deploying the ForgeRock Identity Platform on Kubernetes.

The LDIF importer is no longer used in CDM and CDK deployments.

Building your own ldif-importer Docker image is no longer required when deploying the ForgeRock Identity Platform on Kubernetes.

The ds-idrepo-2 replica is now deployed as part of the CDM for failover purposes.

Previously, IDM was not able to use a third ds-idrepo replica, so the number of ds-idrepo replicas was set at 2. A recent enhancement to IDM lets additional replicas be used for failover, so a third replica has been added to the CDM architecture.

Small CDM clusters now have 2 AM pods. Previously, they had 3 AM pods.

The Release Notes now document the limitation that the CDK and CDM are not preconfigured to support IDM’s workflow engine.

Note that this limitation has existed since version 7.0 of the platform, when the CDK and CDM starting using DS as the IDM repository.

The forgeops install command now installs cert-manager as part of CDK and CDM deployment.

Because of this, the steps for configuring the CDK and CDM to use a certificate from a CA have changed. See TLS certificate for details.

The new cluster/minikube/cdk-minikube utility lets you create a Minikube cluster that’s configured for running the CDK.

The Minikube cluster page now includes an example of how to run this utility.

It’s now recommended that you use the Hyperkit driver for Minikube clusters on macOS systems, and the Docker driver for Minikube clusters on Linux systems.

ForgeRock has tested Minikube clusters with these two drivers, and the new cluster/minikube/cdk-minikube utility creates Minikube clusters with these two drivers by default.

CDK deployments on Minikube now require you to enable the volume snapshots plugin. See Minikube cluster.

Use the new amster import command instead of the config.sh import command to import sample AM run-time data to the CDK.

The new forgeops repository feature evolution section has been added to these ForgeOps 7.3 release notes to clarify the meaning of feature statuses, such as technology preview, evolving, legacy, deprecated, and removed.

Version 7.1.0 of the forgeops repository is available in the release/7.1.0 branch.

Previously, release tags were used for forgeops repository releases.

The Docker images that implement UI elements in the ForgeRock Identity Platform are now supported for use in production deployments. For more information, see Base Docker images.

Previously, users were required to build all the Docker images for the platform for use in their production deployments.

The section, Third-Party Kubernetes Services in Support from ForgeRock has been revised.

Inbound communication to DS instances now occurs over secure LDAP (LDAPS). Previously, communication was over LDAP connections.

Previously, IDM was deployed as a stateful set.

The bin directory in the forgeops repository now contains scripts written in Python 3.

Python 3 has been added to the list of third-party software that you need to install before using the forgeops repository. Note that Homebrew users can install Python 3 using the command, brew install python.

Some of the functionality available in bash scripts is replaced by the identical functionality in Python scripts. No functionality has been removed with these script changes:

A new step to configure the Secret Agent and create secrets is required when deploying the CDM.

The new step—running the kubectl apply command—has been added to the CDM Cookbooks.

Previously, this was done automatically by the skaffold run command.

Note that Skaffold still automates secret creation when you deploy the CDK.

Support for volume snapshots has been added to the DS operator technology preview. For more information, see the DS operator README.

Configuration expressions used in an AM configuration profile are now preserved in that profile after you export a configuration from the CDK to a forgeops repository clone.

For more information, see About property value substitution in the CDK documentation.

CDK and CDM deployments are now verified on newer Kubernetes versions. For more information, see Validated Kubernetes versions.

The Secret Agent operator now supports changing individual administration passwords. If periodic password changes are a requirement for your organization, you can change individual administration passwords as needed.

The ds-idrepo-2 replica is no longer deployed as part of the CDM.

IDM did not use this replica, and removing the replica improved replication performance for the CDM, and lowered the cost of the deployment.

CDM backups are now taken from the ds-idrepo-0 and ds-cts-0 DS instances by default.

In previous versions, backups were taken from the ds-idrepo-2 and ds-cts-2 DS instances by default.

With this change, you must explicitly configure a region when you run one of the CDM cluster creation scripts. For details, see the environment setup sections for Google Cloud, AWS, and Azure.

Previously, CDM clusters were created in specific regions by default.

Long form command-line options are now available for the ingress-controller-deploy.sh command. To see the available options, run /path/to/forgeops/bin/ingress-controller-deploy.sh --help.

The CDK documentation now includes an optional step for adding a secret to CDK deployments. The secret contains a TLS certificate issued by an external certificate authority (CA), or by a local CA that you create using the mkcert utility. Users who access ForgeRock web-based applications on deployments that have this type of secret do not need to accept a self-signed certificate.

The export and sync options of the config.sh command let you export AM run-time data from a running CDK instance to a configuration profile stored in a local clone of the forgeops repository. With this release, the export and sync options can now export all of these types of run-time data:

In previous releases, only OAuth 2.0 clients and IG agents were exported.

Two benchmarks are available for ForgeRock Identity Platform version 7:

Contact your ForgeRock sales representative to obtain our results for benchmarks for these ForgeRock Identity Platform version 7.

For simpler deployments, small and medium CDM clusters now use a single node pool for all pods instead of using a second node pool for DS pods.

Large CDM clusters continue to use two node pools.

The CDK and CDM documentation has been improved! New checklists help you navigate through set up and deployment activities:

Task maps are provided with each set up and deployment activity. They help you determine where you are in the deployment process, and indicate the next step you’ll perform.

ForgeRock now recommends that you start Minikube with the cni=true option. Starting Minikube with this option circumvents Minikube issue 1568, which required users to run the Minikube VM in promiscuous mode.

In Minikube cluster:

CDM has been tested on newer versions of Kubernetes. See Validated Kubernetes versions for details.

Secrets for both the CDK and the CDM are generated dynamically when they start up. To obtain the secrets, run the print-secrets.sh script.

For example, to obtain the amadmin user’s password:

Several new pods, deployed in both the CDK and the CDM, handle common user interface functions. The new pods are named admin-ui, end-user-ui, and login-ui.

The new version of the CDM starts three pods.

Previous versions of the CDM started a single AM pod. After CDM startup, you restarted the AM pod, and then ran the kubectl scale command to scale the number of AM pods.

CPU and memory requirements for running the CDK on Minikube have increased:

Because Dockerfiles for the base Docker images no longer reside in the forgeops repository, the steps for building base Docker images have changed. See Base Docker images for the new steps.

Accessing the IDM REST API now requires an access token issued by AM. See Access the IDM REST APIs in IDM Services for an example.

This revision uses Skaffold and Kustomize, instead of using Helm charts, to deploy the platform.

Skaffold can detect changes to the file system that holds the AM, IDM, and IG configurations. When it detects a change to one of those configurations, it rebuilds the am, idm, or ig Docker image. Then, it reorchestrates the ForgeRock Identity Platform deployment.

Note that changes to dynamic AM configuration data—policies and application data—are not automatically detected by Skaffold. Changes to dynamic AM configuration data still need to be exported using Amster.

For more information about customizing the ForgeRock Identity Platform configuration when working with Skaffold, see Docker Image Development.

In the new revision, CDM deployments use three availability zones and two node pools.

In previous versions, CDM deployments used two zones and a single node pool.

This revision includes improved bash scripts for installing the NGINX ingress controller, Certificate Manager, Prometheus, Grafana, and Alertmanager in a CDM cluster.

The new scripts are ingress-controller-deploy.sh, certmanager-deploy.sh, and prometheus-deploy.sh.

Although the CDM still uses Helm charts to install the NGINX ingress controller and Prometheus, a Helm tiller pod is no longer needed in the CDM cluster.

In the previous version, CDM deployment required a running tiller pod to support Helm chart deployment.

This revision uses Gradle to trigger AM and IDM simulations for benchmarking performance.

In this revision, backup is greatly simplified. Backups are made to local disks running in the same pods in which DS runs.

The previous version required an NFS-mounted external storage device (Google Filestore or EFS) to be available for backup. The external storage device is no longer needed.

For more information, see CDM architecture.

In this revision, IG is not deployed as part of the CDK or CDM, and benchmarks for IG performance are no longer published in the CDM Cookbooks.

You can still deploy IG with the CDK or CDM; use the Kustomize base and overlays in the /path/to/forgeops/kustomize/ig directory.

The CDM Cookbooks provide the steps for creating medium-sized (10,000,000 users) clusters.

You can still create small-sized (1,000,000 users) and large-sized (100,000,000) clusters using the artifacts in the forgeops repository.

Benchmarks for small, medium, and large clusters are available for Google GKE. Benchmarks for medium clusters only are available for Amazon EKS and Microsoft Azure AKS.

The CDM and CDK use administrator passwords that are randomly generated by the secrets generator.

See the UI and API Access pages in the CDM and CDK documentation for information about how to obtain the administrator passwords.

ForgeRock’s Docker image repository names are now am, idm, and ig. In previous versions, the Docker image repository names were openam, openidm, and openig.

Kubernetes pod names now include the strings am, idm, and ig. In previous versions, the pod names included the strings openam, openidm, and openig.

As with previous versions, you must still build your own base Docker images for the ForgeRock Identity Platform for production deployments on Kubernetes.

In this version, you must download the ForgeRock binaries manually before building the Docker images.

In the previous version, a script automatically downloaded the binaries from ForgeRock’s Artifactory repository. This script has been removed from the forgeops repository.

For more information, see Base Docker images.

The customize-am.sh script is no longer available in this revision of the forgeops repository.

To customize the AM web container in this revision, add instructions to the am Dockerfile to copy your customizations into the /usr/local/tomcat/webapps/am directory.

The new backup-loader.sh script lets you create PVCs from DS binary backups before you start the platform, so that DS instances in the platform use the data from the PVCs.

Use the following default URLs to access ForgeRock Identity Platform services in this revision:

The CDM includes more recent versions of these third-party components.

See these scripts for details about versions of third-party software currently used with the CDM: ingress-controller-deploy.sh, certmanager-deploy.sh, and prometheus-deploy.sh.

Support for self-signed certificates and signing certificates is built into the CDK when it runs on Minikube. Because of this, you no longer need to deploy Certificate Manager when deploying the CDK on Minikube.

CDM deployments use Certificate Manager for TLS support. In previous versions, Certificate Manager was configured to call Let’s Encrypt to provide certificates for CDM deployments on GKE.

In this revision, Certificate Manager is configured to provide a self-signed certificate for CDM deployments on GKE.

The DevOps Developer’s Guide has been replaced with two new guides:

The content in the new guides is similar to the DevOps Developer’s Guide. Each of the new guides limits its descriptions to a single type of cluster, thus simplifying procedures.

The information formerly in the Before You Deploy section of the Release Notes has been moved. This information is now available where it’s needed instead of on linked pages.

The DevOps QuickStart Guide tutorial has been removed from the documentation.

ForgeRock supports CDK and CDM installation on Linux and macOS only. If you use a Microsoft Windows computer, you’ll need to create a Linux virtual machine for installing the CDK and the CDM.