Github App used for Authentication is Removed after upgrading to 2025.1 LTA Version

We are planning to upgrade our developer edition of sonarqube from 10.0 to 2025.1 LTA version.

We tested the upgrade by setting up a local server with 10.0 version and upgraded it to 2025.1 LTA version. However, after the upgrade it seems that the Github App which has been already configured for Authentication has been removed (Administration > Authentication > Github) and below warning message is displayed.

Compatibility with GitHub OAuth Apps is deprecated and will be removed in a future release. As such, your current configuration will continue to work but some features will no longer be available. We recommend that you create a new GitHub App configuration. This will automatically replace your current GitHub OAuth App configuration.

We have below inquiries :

  1. In our existing configuration of Github Authentication, we are using Github App which has been created for Devops Integration and not Github OAuth App. Even though it’s not Github OAuth App, the config has been removed. Is this the intended behaviour ?
  2. We are already using Github app for Devops Integration. So, we would like to know if we can configure the same github app for Authentication
  3. Do we need to consider anything apart from the github app for facilitating Authentication via Github

Hey @Naveen_Sundarrajan!

In SonarQube v2025.1 LTA, if your GitHub Authentication configuration lacks an Application ID, SonarQube takes that as a sign that legacy configuration was used.

Personally, I don’t think it’s a great experience that you lose the ability to see the existing configuration, but in my tests, the existing configuration is still there and continues to work. However, SonarQube will push you to create a new, valid configuration.

You can, and should, re-use the existing application that you use for the DevOps Platform Orchestration (which orchestrates project onboarding and PR decoration) for authentication. This is what we document.