Archive

Enhancements

• For more governance concerning usage of tools, customers can now opt in for some restrictions concerning editing and viewing tools in projects. When the first feature toggle is enabled, only Portal Admins can add tools to projects, but Project Admins cannot. In addition, another feature toggle is available, which defines if unassigned tools for users or projects can be viewed on the respective detail pages. Users, who have edit rights, will always see all available tools independently of this switch.
• Customers can opt in to define a default project for which new users will automatically receive a VIEWER role. While this can be used to offer internal documentation at a central place, it has the disadvantage that it weakens the data privacy implemented by organizations. If users have a role in the same project, they can see each other in the DevOps Portal, even when they are in different organizations.

Improvements

• Grafana is now a default tool. This means, it is preselected as a tool when new projects or users are created.

Bugfixes

• Some pixels were cut from the icons in the main menu on the left-hand side.
• Minor text fixes in notification mails.
• An issue happening just for some customers was fixed, which could redirect back to the users page when typing something on another page.

Enhancements

• Implemented Just-in-Time (JiT) provisioning for users authenticated by external identity providers (IdPs).
• It's now possible to manage Rancher Tech Users in the Portal. Assigning a Rancher Tech User to a project will only make it visible to the project members. It will not get automatically access to any cluster resources in Rancher. For this, you have to manually assign cluster roles to the "local" copy of the Tech User in Rancher. Login with the Technical User Name (without any '@domain' suffix). The page Creation of API Tokens for Technical Users shows the next steps which are necessary before you can use your Rancher Tech User for API calls into Rancher.

Improvements

• Reduced number of external dependencies in own code.
• Improved German translations of notification emails.

Bugfixes

• Fixed visibility for Dependency Track projects, so that it works for all versions of an analyzed project.

Enhancements

• A new "Reset 2FA" button has been added to the user details page and is also available in the More menu on the users page. Reset 2FA makes sense, when a user switched to a new mobile phone but forgot to back up the 2FA code configuration.
• Prepared the DevOps Portal to support external identity providers (IdPs) in the future.
• Since gitlab implemented a soft delete for organizations, the consequence is, that projects deleted in the DevOps Portal will stay for 7 more days in gitlab. Since this would block creating a new project in the portal with the name that was previously used, the DevOps Portal is now renaming deleted organizations in gitlab to a unique name to avoid any collisions.

Improvements

• The aggregation logic for collection projects in Dependency Track has been changed to sum up the number of findings of sub projects only when they are marked as "last version".
• Updated the Portal to Angular v20.
• The optional feature for automatically locking inactive users has been improved and is now sending mails with dates formatted to the locale of the user.
• Improved pod affinity settings to avoid scheduling problems after cluster restarts.
• Improved design of project and tech user delete dialogs.

Bugfixes

• On the Tech User edit page, the flickering caused by the password strength check has been fixed.
• Fixed a bug in the localization that could lead to UI errors for some users.