SSO enable for Sonarqube community edition and developer edition

SonarQube Server / Community Build
1

Must-share information (formatted with Markdown):

  • which versions are you using (SonarQube Server / Community Build, Scanner, Plugin, and any relevant extension) 25.1.0
  • how is SonarQube deployed: zip, Docker, Helm - Docker
  • what are you trying to achieve - we are trying to enable SSO for our Community and developer edition
  • what have you tried so far to achieve this- No, we need to know whether its possible or not.

Do not share screenshots of logs – share the text itself (bonus points for being well-formatted)!

2

Hi,

Welcome to the community!

Only the latest version of SonarQube Community Build is considered active, so you’ll need to update and see if the situation is still replicable before we can help you.

Your update path is:

25.1 → 26.1 → 26.4

You may find these resources helpful:

If you have questions about upgrading, feel free to open a new thread for that here.

And to answer your question, yes this is possible.

 
HTH,
Ann

3

@ganncamp Thank you for the update.
Could you please confirm if we can proceed with the upgrade for the other instance, specifically the SonarQube Developer Edition? Additionally, could you share any guidance or documentation for SSO implementation?
As a standard practice, we typically upgrade only to LTA (Long-Term Active) versions, and we understand that version 26.4 is not an LTA release.

4

Hi,

For Community Build, there is no LTA. Explicitly: we don’t patch Community Build. If you want the fixes, the patches, you upgrade.

You didn’t mention a Developer Edition instance in your first message. Yes, you likely can/should upgrade. What version is it on?

 
Ann

5

We are currently on SonarQube Developer Edition version 2025.1.4. Could you please confirm if any features are removed or impacted when upgrading to version 26.1.0?

6

Hi,

Okay, there’s some confusion here. The versioning scheme is different between SonarQube Server, which uses [YYYY].[release] and SonarQube Community Build, which uses [yy].[mm]. So while it would be a higher version to go from 2025.4.1 (which is still supported) to 26.1, it would actually be a downgrade in functionality.

You’re targeting 2026.1.2, which is the current LTA.

Community Edition / Community Build never supported branch and PR analysis. Developer Edition does and always has. There are no significant removals from 2025.4 to 2026.1 that spring to mind - only exciting new functionality. :partying_face:

 
HTH,
Ann

7

Thank you for your response and for clarifying the version. We are currently using SonarQube Developer version v2025.1.4. Can we upgrade directly to v2026.1.2?

8

Dear @Thilagam_Subburaj,

Based on the documentation you can directly upgrade to 2026.1.2.

Cheers :baby_bottle:

9

@EclipseWizard Thank you. Could you please confirm whether SSO can be implemented in SonarQube Community Build version 26.1.0?

if yes, can you please share any documentation for that.

10

HI @Thilagam_Subburaj,

As previously stated, yes, you can implement SSO with Community Build. The docs should help.

 
Ann