@nandjelkovic @rybowdenAccess There’s an updated version of the extension here: SLVS-2383 Testing different credential store implementations · SonarSource/sonarlint-visualstudio@373b5be · GitHub It includes the changes from the latest release, alongside the experimental code for credentials storage
2 Likes
I used this: install vsix as admin - Search you need to open the command prompt as elevated and the /admin command will install for all versions and work.
Can confirm the new version still works all good for me 
2 Likes
@nandjelkovic Did you have any luck installing the extension? I would like to get feedback from you, before I can commit to the implementation
Hi Georgii.
I managed to install new extension version (9.1.0.15776) in my Visual Studio 2026 elevated access ran instance. I did it using Private extension Gallery. I managed to create connection to SonarQube server using both DPAPI options.
You can find attached logs.
Thank you!
Output-SonarQube-DPAPI-MasterPassword.txt (25.6 KB)
Output-SonarQube-DPAPI.txt (4.6 KB)
The second log file seems to be from the default credentials provider, just to double check: is it the wrong attachment?
I’m more curious about the DPAPI without password case (it should use DataProtectionScope.CurrentUser instead of LocalMachine in the case of DPAPI with password), as entering the password every time will be quite bad in terms of UX. I know you’ve already said that it works, but I just want to be extra sure and check the logs before we commit to bringing this to production.
Understood. Take a look at this one if it’s ok, please.
Output-SonarQube-DPAPI-01.txt (1.4 KB)
1 Like
Can confirm been using this for over a week now and SonarQube is still connecting and working fine on the without password option. I have not had to add the token in again or anything it is just working every time i open up VS.
We have an issue with binding solution to project on SQ server. Adding connection was successful but binding is failing.
Uploading new log file.
Output-SonarQube-ErrorBoundProject.txt (99.6 KB)
Could you delete the connection and try with DPAPI+Password?
I will prepare a build to test a theory I have just in case it’s only the DPAPI is broken
I have a suspicion that encryption might not be working as expected. For debug purposes, I added logging of the last two digit of the SQ token just to check that they match with the original: SLVS-2383 Testing different credential store implementations · SonarSource/sonarlint-visualstudio@ac5a684 · GitHub
Could you run this build and see if that’s the case?
These are two log files using new build, DPAPI and with Password:
Output-SonarQube-DPAPI-UnableToBindProject.txt (87.6 KB)
Output-SonarQube-DPAPIWithPassword-UnableToBindProject.txt (136.4 KB)
Can you please run it again and check Token ends with log messages to see if this matches the token you’re providing? I want to make sure it decrypts the correct data
@nandjelkovic Hi. Did you have a chance to verify this?
Can you please run it again and check
Token ends withlog messages to see if this matches the token you’re providing? I want to make sure it decrypts the correct data
Hi. I have checked log, last two characters in token ends with match token we’re using. When I try to unbind solution and bind again I receive error already screenshotted you.
Can you try to use Generate Token button when creating the connection just to verify that the correct type of token is created?
Hi @nandjelkovic Any updates on this?
Hi, for this option I need assistance from our Dev team since I don’t have permissions to generate tokens. I was trying to assist and interfere with our Devs work process as little as possible, but for this one I need to plan testing with some of them, install and test latest custom build. I will try to schedule session on Monday.
Thank you!