MDM 16.3.1 Upgrade Notes
Keycloak logout and Content-Security-Policy
| Applies to 16.3.1-patch28 and later. |
The MDM Web App and the MDM Web App Admin Center now send the Keycloak logout request as a POST form instead of a GET redirect.
If a reverse proxy in front of the application, or the application’s own security header configuration, sets a Content-Security-Policy header with a form-action directive, add the Keycloak origin to it.
Otherwise, the browser blocks the logout request and users stay logged in.
form-action 'self' https://keycloak.example.comIf your deployment doesn’t add a similar directive, no action is needed.
Configuration changelog
This section provides information about the changes in the configuration files that need to be taken into account when upgrading the solution. In certain cases, the newly introduced default is used or some configuration is required.
The following table lists the configuration files that were added, changed, or removed.
| Added files | Changed files | Removed files |
|---|---|---|
/ |
|
/ |
The following sections list the changes in the files: added, changed, and removed properties.
MDM Server application.properties
Changed properties
-
ataccama.one.mdm.inlist.db.settings.use-postgres-copy-command- default changed fromfalsetotrue. For details, see MDM Server Application Properties > Database performance.
runtime.properties
Changed properties
The following runtime parameter defaults have changed.
The new defaults apply only if ataccama.one.mdm.inlist.db.settings.use-postgres-copy-command is set to true (the default in version 16.3.1).
For details, see Runtime Parameters.
-
nme.db.batchSize- Default changed from100to10000. -
nme.vldb.batchSize- Default changed from100to10000. -
nme.vldb.inList.batchSize- Default changed from1000to100000. -
nme.vldb.commitSize- Default changed from-1(unlimited) to10000. -
nme.db.inList.batchSize- Corrected default:100000.
Was this page useful?