Upgrade from version 4.2.1.x to version 4.2.1.12/4.2.1.13 in Docker
The upgrading process to the newest OpenIAM version of 4.2.1.12/4.2.1.13 is simple and straightforward, following the steps below.
- Connect to the Linux Host and verify if containers are running by running the following command.
docker ps
- Navigate to the OpenIAM Docker Compose directory with the following command.
cd /root/openiam-docker-compose
- Check the Git Status and create a backup branch by running the following commands.
git statussudo git checkout -b RELEASE-4.2.1.10-changessudo git add .sudo git commit -a -m "4.2.1.10-changes"
- Create a new branch for the upgrade and merge changes by running ...
sudo git checkout -b update_to_RELEASE-4.2.1.12sudo git pull origin RELEASE-4.2.1.12sudo git merge origin/RELEASE-4.2.1.12
The commands above can be used for 4.2.1.13 version of OpenIAM as well, depending on what version you are to upgrade to.
Note: There may be merge conflicts when switching Git branches. Please follow this link for guidance.
- Stop and remove all running containers with the following command.
sudo ./shutdown.shdocker ps # Ensure all containers are deleted
- Export container registry credentials with the following.
export DOCKER_REGISTRY=confidant-bhaskara.container-registry.comexport DOCKERHUB_USERNAME=test.upgradeexport DOCKERHUB_PASSWORD=XXXXXXXXXXXXXXXXX
- Run setup and start OpenIAM commands below.
sudo ./setup.shsudo ./startup.sh
- Verify the running containers, repeating the command in step 1.
docker ps
Once all the services are up and running, login to OpenIAM and navigate to Administration > About OpenIAM.
The build version must be updated to 4.2.1.12/4.2.1.13.
Note: You must update connector if you use newer versions of the product. It is recommended to use the latest connector version.
All .NET/PS connectors versions as at 5.24.0.0 version are backward compatible, hence updating it will not disrupt operation of OpenIAM versions 4.2.0 and higher.
All .NET/PS connectors versions as at 5.24.0.0 version are backward compatible, hence updating it will not disrupt operation of OpenIAM versions 4.2.0 and higher.