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.
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.
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.
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!