Request for Reintroduction of OIDC Protocol Support

SonarQube Server / Community Build
1

Version： Community V10.8
Deploy： Docker

Hi Team,

We previously integrated with SonarQube using a plugin based on the OIDC protocol. However, after upgrading to version V25.1, the new version no longer supports the OIDC protocol, which has rendered our existing identity provider login method inoperable. Furthermore, our identity provider does not support the SAML protocol.

We are wondering if there is a solution to this and whether OIDC protocol support can be reintroduced.

Thank you.

Best regards

2

Hey there.

I guess you were using sonar-auth-oidc/sonar-auth-oidc. It looks like there are some users supporting a fork of sonar-auth-oidc:

That might be worth a try! On our end, built-in OIDC support is not currently on our roadmap.

3

That is certainly a shame. It is not a difficult implementation. Much easier than SAML and is widely supported across the industry. I realize that this has been the default position for a number of years - but seriously - it’s time to have a discussion with the development team and get this done.

The forks of the plugin do not have any serious community effort behind them. OIDC is basically a dead end at this point. Without OIDC support, we will mostly likely drop this product and seek an alternative.

6

Hey @kingsixty

I’m not discounting what you have to say about official support (and I’ve flagged it for attention), but I would like to mention that the community-supported plugin has been updated to support the latest SonarQube versions.

7

Sadly I cannot agree more here. Lacking OIDC support was a pain point when we switched from (old good LDAP) to SSO on our infra tooling

8

As an Information System Security Officer and an administrator of SonarQube Enterprise at a federal agency, I would love to see support for OIDC

10

Thank you for the feedback – it’s truly appreciated.
Currently, OIDC support is planned for SonarQube Cloud in early 2026. There are no immediate plans to support it on SonarQube Server at this time, but I’ve noted the feedback shared here, which is adding more traction to the case for supporting it on SQS in the future. Stay tuned!

12

Will the OIDC support cover the ability for CI/CD integrations to send manual analysis without needing an API token? Or is this only for user integration?

13

This is tracked on the Product board: https://portal.productboard.com/sonarsource/3-sonarqube-server/c/685-use-oidc-to-set-github-actions-analysis-instead-of-secrets

14

I’m still wondering why after many year OIDC support is still not included (at least in the Enterprise edition).

Specially now with MCP that fully support Authentication/Authorization flow ( Understanding Authorization in MCP - Model Context Protocol )

Forcing user to generate an API key make it difficult to scale AI/MCP adoption specially in large companies (AI gateway, MCP gateway, Centralized token issuer (like Keycloak), etc…)

Many other “DevOps/CI/CD” products provide such support already (Atlassian/Bitbucket with incoming links, JFrog/Artifactory with OIDC integration, Spotify/Backstage (OpenSource do clearly better here etc… and many more… But for some reason not SonarQube)

What we lack

  • User login using OIDC
  • Validate Bearer/JWT token for API access (MCP support, CI/CD integration)

As a platform engineer supporting thousand of user it’s starting to be difficult to justify this lack of support in 2026.

Hope it will again ring a bell in Sonar

15

Hey @jonesbusy ,

Sorry for the long delay to get an answer.

Actually, we released OIDC support for SonarQube Cloud about at the same time of your last message: 🚀 New: OIDC SSO for SonarQube Cloud Enterprise now in general availability!

I hope this covers you needs :slight_smile:

Cheers,

Aurélien

ps: enhancing the experience for MCP authentication is on our roadmap as well