Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Several improvements were made in this area. The main improvements are that we have added a introduced the new Editor role that sits between , offering more privileges than the existing Viewer and Administrator roles in capabilities and that all application parts that make up iDNA applications are now accessible using configured LDAP credentialsrole but fewer than Administrator. All roles are now verified through LDAP credentials (if configured) for accessing iDNA application components. Please see the LDAP Setup Guide for more details on how to configure LDAP authentication.

...

Revamped LDAP Access
The existing option to access the iDNA portal with LDAP credentials has been improved and extended to the Admin Client and DataMiner. The configuration dialog remains largely unaltered within the iDNA portal under [Settings → LDAP Settings].

Metabase continues to use its own authentication system, which is configured separately in the Metabase Admin portal.

The one small change that was made tothe config dialog was the addition of the role mapping for the new Editor role.

...

Metabase has been upgraded to version 50.x in this release. The main purpose was implementing bug fixes and security updates, but and also an updated look and feel as well as several usability improvements are also available in this new version. See the Metabase 50 Release Notes for more information.

...

A significant change in version 50 is a revamp of Metabase's permission system, which aligns with iDNA's own, as described above. For this reason, the first time an iDNA version >= 3.2.0 is installed, a reset of Metabase permissions is performed automatically in the background. This should not inconvenience the majority if of iDNA customers. In rare cases where custom permissions for non-panagenda dashboards or questions are defined, these permissions have to be re-created using the new Metabase access control interface.

...

Metabase Access: Users with Viewer access previously had issues with accessing all dashboards. This was fixed as part of the above-mentioned Metabase access structure changes.

...

Metabase LDAP Role Mapping: Depending on the LDAP server's schema, automatic role mapping may not function as expected. A simple work-around workaround is to manually assign users to the appropriate groups inside Metabase. LDAP authentication in general is not affected.

...