Hi @FlorentB,
This is indeed a breaking change we introduced in the latest release. Searching certificates at the OS level was causing too many problems on Windows, so we decided to stop doing that (see this ticket for more details).
And you are right, SonarLint now expects users to provide a few system properties, as described in the link you shared.
One thing that you missed is that SonarLint expects a separate trust store file to exist on disk, containing your certificate. You can find instructions on how to create a trust store and add your certificate to it on the web, there are a lot of tutorials. The following command should do the trick:
keytool -import -keystore C:/path/to/your/truststore -storepass password -noprompt -alias sonarqube-ssl -file your_certificate.cer
Then the last step is to provide the required system properties (the eclipse.ini method should work):
-Dsonarlint.ssl.trustStorePath=C:/path/to/your/truststore
-Dsonarlint.ssl.trustStorePassword=password
-Dsonarlint.ssl.trustStoreType=PKCS12
Please note that the first property differs from what you shared earlier: sonarlint.ssl.trustStorePath.
Please also note this is assuming the SSL certificate you mention is a server certificate and not a client certificate. If it’s a client certificate, what you need to create and configure is a key store.
Hope this helps