v2.3.1 Upgrade Notes

Configuration Changes

Container Image Versions

Replace docker-compose.yml with new version from release folder.

Update container versions in .env to v2.3.1 and pull the new container images from the container registry.

Installation Package for Running MOPS 4.0 without Docker

MOPS 4.0 v2.3.1 introduces an installation package that allows you to install MOPS 4.0 to run without Docker. If you are using the containerized version of MOPS 4.0, you can choose to switch to the new installation package. Follow the instructions in Installation with Windows Services to install MOPS 4.0 using the new installation package.

Installing using Windows Containers is still supported in this version.

Directory Database

You should run the update script for the directory database.

See Upgrade Directory Database - Step 3.

Upgrade Notes

MOPS 4.0 v2.3.1

[MD-2026] Accounts which doesn’t get an initial “last session start” are not getting updates

NOTE: This system update will automatically be applied when you upgrade to MOPS 4.0 v2.3.1 using standard database upgrade scripts, and there is no manual action needed for this update.

[MD-2187] Keycloak (Admin UI) requests should not be cached

Manual changes are only needed for the Container based installation:

In conf/ingress/rules.json, remove the middleware named “cache-headers” in “http” -> “routers” -> “keycloak” -> “middlewares”.
It may be necessary to do a hard refresh/empty cache in the Keycloak admin interface on “/auth”.