Archive

Last modified by DOaaS Operator on 2025/02/05 11:50

Blog - posts for November 2024

Nov 28, 2024,

All users will need to set new passwords following a communicated wave planning. Automated mails are sent out as usual in the following weeks, so that every user is notified about the expiration date of his/her current password. When the users set new passwords, they will be stored in Keycloak instead of the LDAP server.
Any technical user or token will continue to work for authentication.
The symbols '!' or '?' are no longer displayed next to the user status to symbolize a status like e.g. locked in LDAP server.
LDAP is no longer listed on the Health Checks page for Portal Admins.
The documentation page DevOps Portal for Users has been updated to describe the new activation and password change workflows.

Nov 14, 2024,

When a user is created or edited, a new global role on Jenkins can be granted or removed.
When the box is checked, the user is added to the agent-admin role in Jenkins. This role can be used to add and remove agents to the Jenkins controller. Existing agents can be connected and disconnected. Please note, that the permission for configuring agents is not included in the role. Therefore, if you want to reconfigure one of your self-hosted agents, simple remove the agent and add it again with the new configuration. For more information, see Connecting Inbound Jenkins Agents.
To be able to remove the LDAP-Server from the toolchain, several changes have been implemented:
- Tools which require an LDAP-Server are now using our self-developed LDAP-Adapter, which simulates an LDAP-Server with Keycloak as the real backend.
- The password change was moved from the Portal to Keycloak.
- Activating a user by clicking on the link in the mail is still managed by the Portal, but setting the initial password is now done in Keycloak.
- Automated testing can now also test workflows which include the sending and reception of emails.

Made sure that the DevOps Portal can handle a large amount of data returned by API calls of Gitea.
The invitation email for new users is now both written in English and German language.
When a portal or project admin calls resync on a project, this action is now recorded in the audit log.
Reduced number of backend calls on the Portal homepage.
Simplified configuration of Jira schemes solely based on scheme names.
Spring Boot update

For customers who use Gitea also for source code management, the additional Gitea tile is now properly displayed before the CI/CD tile and not next to the Artifact Repository tile.
When a reversed sort order was used for the project role column on the users page, it was not correctly memorized for later visits of the same page.
A bug prevented the complete deletion of old scan results in SonarQube when the project was deleted in the Portal.
If a user logs in to Harbor without having the tool assigned, it works, but of course no projects are visible. When Harbor is later assigned to the user and the user logs in to Harbor, an error occurs due to an inconsistency of the user id. This is now prevented by deleting wrong user ids in Harbor, when the tool is assigned to a user.