Issue with email configuration post 2025.1 upgrade

SonarQube Server / Community Build
1

Hi there,

Our organisation is in the process of preparing to upgrade our SonarQube Enterprise instance, which is currently on version 10.6, to the latest 2025.1 LTA release.

We have a test instance to allow us to experiment with the upgrade process and performing the same update from 10.6 to 2025.1 has revealed an issue with the way email configuration settings are now handled.

We utilise the ability to encrypt settings values (via the api/settings/encrypt API) so they are stored securely, i.e. not in plain text, within the SonarQube database. In particular we do this for the email.smtp_username.secured and email.smtp_password.secured settting values.

However upon migration of those encrypted settings to the new email configuration format in 2025.1, the SonarQube server can no longer send emails and now logs authentication errors instead.

I have confirmed that if we use unencrypted values then the server is able to send emails without issue.

I’m just wondering if this is an oversight? Surely we’re not the only users of SonarQube that don’t desire credentials for external systems to be stored in plain text within the SonarQube database?

I look forward to your response.

Thanks,

Sam

1 Like
3

Hey @Sam_Anthonisz

Thanks for bringing this to our attention. Indeed, there have been some changes in SonarQube to how e-mail configuration is set and stored, and I wouldn’t be surprised if settings encryption (well, decryption) was overlooked in this case.

I’ve escalated this internally and will come back when I have more information.

2 Likes
7

Hey @Sam_Anthonisz

You can track updates on this at SONAR-24350. We will fix this on master and then evaluate a backport (it’s very likely).

1 Like