Page History
...
Table of Contents |
---|
Improvements
Revamped user access and role framework
Several improvements were made in this area. The main improvements are that we have added a new Editor role that sits between the existing Viewer and Administrator roles in capabilities and that all application parts that make up iDNA applications are now accessible using configured LDAP credentials.
...
- Create/Manage Source Code Insights
- Edit custom properties for DB Instances and Replica Sets
- Create/Manage DataMiner queries
- Create/Manage Metabase dashboards and questions
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 to in the config dialog was the addition of the role mapping for the new Editor role.
Major Metabase upgrade to new version
...
Metabase has been upgraded to version 50.x in this release. The main purpose was implementing bug fixes and security updates, but and 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 be no inconvenience to the majority if 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 permission interface.
Optional SNMP discoverability package
...
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.
Known Issues
Metabase LDAP Role Mapping: Depending on the LDAP server's schema, automatic role mapping may not function as expected. A simple work-around is to manually assign users to the appropriate groups inside Metabase. LDAP authentication in general is not affected.
Structural Changes / Upgrade Path
...