SonarLint for VSCode 3.11 - Easy authentication to SonarQube

Hello VSCode users,

With this release of SonarLint, we’re completing a round of improvements to make SonarLint connected mode setup a no-brainer for all developers working in a team. In previous versions:

  • We’ve added a user interface to setup your connections to SonarQube and SonarCloud, and to bind your local folders to remote projects
  • Next, we’ve made the binding process even simpler by adding automatic binding suggestions

In this release, we’ve worked to simplify the authentication process to SonarQube. Instead of manually generating an authentication token in SonarQube and providing it to SonarLint, you’ll simply need to:

  • click on the “Generate token” button in the connection wizard:


  • Confirm you want to connect SonarLint with SonarQube

That’s it, the token is automatically generated and securely stored, and your connection is ready to use! In order to benefit from this improvement, you need to update SonarLint to version 3.11 and SonarQube to the newly released 9.7 version.

Among the other highlights of this release, we’ve added support for TypeScript 4.8 and for PHP 8.2

Please note that starting from this release, SonarLint requires at least version 14.17 of Node.js to run JS and TS analysis

You can find more information in the release notes.


Very cool. Question in the same vein, can you support proxies in the SonarLint program? Right now we still have to set JAVA_TOOL_OPTIONS globally to enable SonarLint to connect using our proxy.