RDM 16.3.1 Upgrade Notes
Keycloak logout and Content-Security-Policy
| Applies to 16.3.1-patch28 and later. |
The RDM web application now sends 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.
Added metric for tracking number of users in web application
A new ataccama_one_rdm_user_activity metric was added that tracks the number of unique non-technical users who initiated any action (for example, login) in the RDM web application in the last 24 hours.
See RDM Monitoring Metrics.
Configuration changelog
This section provides the 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 |
|---|---|---|
/ |
|
/ |
RDM application.properties
Added properties
-
ataccama.one.rdm.technical-user-regex-filter- default:^(orchestration-user|monitoring-user|service-account.*)$.A regex pattern used to identify technical users. Users matching this pattern are excluded from the
ataccama_one_rdm_user_activitymetric, which counts unique non-technical users active in the last 24 hours.
For details, see RDM Application Properties.
Was this page useful?