Sudden Auth request

[Jopp-gh]

Hi there,
In the past 3 days Vscodium is asking regularly for my login key and I'm perplexed what happened to trigger this request.

Also... for what reason Vscodium would need login credentials?

I usually don't touch very much the preferences.
What happened to trigger this nagging auth dialog?

[daiyam]

os login or git login? which version and os do you use?

[Jopp-gh]

Well, I resolved by deactivating the build-in extension «GitHub authentication» and also «Microsoft-account» (not relevant to solve my issue, but useless for my case) too.

After this, no auth dialog anymore, it survived simple quit, login and new boot.

Still the question remains:

why did I get this auth dialog in first place?
I'm using Codium for years, know my fav preferences and don't modify them very much. Not that I would remember a recent setting change on my part.
Probably some new defaults in «GitHub authentication», when going online?

[daiyam]

Well, I resolved by deactivating the build-in extension «GitHub authentication» and also «Microsoft-account» (not relevant to solve my issue, but useless for my case) too.

Good!

why did I get this auth dialog in first place?

I don't know. But I did suspect Git but why an OS login auth?
Usually, GitHub authentication is used for oauth request to github by extensions or when a repository is configured with https.
You can look into the log in View/Output and select GitHub authentication in the select box on the right.

[daiyam]

"%cTRACE color: #888 [Main thread secret state] getting password for vscode.github-authentication extension: github.auth”, source: vscode-file://vscode-app/use/share/codium/resources/app/out/vs/workbench/workbench.desktop.main.js (38)
[Encryption main service] checking if encryption is available... 

Ya, it want to authenticate so it seems to look for passwords into the system. It would explain the OS login since the password db would be locked.
The question is why it want to authenticate?

[Jopp-gh]

Ya, it want to authenticate so it seems to look for passwords into the system. It would explain the OS login since the password db would be locked.

Yes exactly! I realized the same, after a break.

Deactivating GitHub authentication and re-activating it again seems to have purged old git settings.
So, no auth dialog anymore, after re-activating GitHub authentication.

I'll add tomorrow if my issue is solved. Then I can say with confidence if GitHub authentication works fine and therefore doesn't need any review.

Why the auth dialog came up at all, will stay a mystery.

[Jopp-gh]

GitHub authentication triggers again! 🤣

It has just a few settings but they cant silence auth request.

Wow... at this point I'll keep GitHub authentication deactivated until I need again GitHub integration.
Currently I've no passion to investigate why this extension pops up.

[itxashancode]

Vscodium asks for a key when it needs to talk to the GitHub‑hosted marketplace or to sync settings.
If you enabled Settings Sync or installed an extension that pulls from the marketplace, Vscodium stores a GitHub personal‑access token in your OS keychain.
A few days ago the token probably expired, was revoked, or got corrupted, so the next time Vscodium tries to reach the marketplace it pops the auth dialog.

Check File → Preferences → Settings, search for sync - if Sync: Enable is true, disable it or re‑authenticate.
Alternatively, open the keychain (macOS: Keychain Access, Windows: Credential Manager, Linux: seahorse or gnome-keyring) and delete any entry named vscodium:github.
Restart Vscodium and it will prompt again, or you can create a fresh token with the repo scope (or just read packages if you only need extensions).

[Jopp-gh]

Hey itxashancode,
thanks for adding useful information to my report.

Vscodium asks for a key when it needs to talk to the GitHub‑hosted marketplace or to sync settings

As far as I can remember, Vscodium didn't ask for passwords, ever. I used the build-in marketplace extensions panel to download whatever I needed to develop code, the marketplace didn't bother me to add keys for it to work. This is desirable, vscode isn't a toy for everyone, so I don't need patronising auth dialogs.

If you enabled Settings Sync

I checked but didn't find an exact setting with this name. Maybe you meant Git: Comfirm Sync as the extension in question for this report was "GitHub Authentication".

Vscodium stores a GitHub personal‑access token in your OS keychain.

There isn't any Vscodium key in my keychain. I just checked and I'm pretty sure there wasn't, ever. All I know is, GitHub Authentication started to ask my login key at the time I wrote this report. I got this annoying auth window after every single launch of Vscodium in a session.

Since I use vscodium only for offline coding and not to sync, this feature isn't important to me. So for the time being I keep GitHub authenticator off.
In future when I need to sync again, I'll see to generate the necessary data.

The request of my report was and is still the need to access Vscodium's application without any auth access, when I'm offline!

Extensions shouldn't be allowed to lock me out, ever:
That's in short, the "bug" I would love to see resolved.

[daiyam]

I would take the post with a grain of salt since Settings Sync doesn't work on VSCodium (it's deactivated since it would use MS infrastructure not available to us...) It seems to be a bit AI generated.

[Jopp-gh]

After updating Vscodium, it's asking once again for my OS login credentials, after each and every app launch (Not os login).
My space isn't a public space, therefore I'm using os auto login and bc of this my os keychain doesn't unlock.

This prompt must be related to plugin security as described in abusing-vscode-from-malicious-extensions-to-stolen-credentials

Electron safeStorage API: “This module protects data stored on disk from being accessed by other applications or users with full disk access

I don't have plugins to store passwords, so why this credential prompt? Just a dumb protocol, to execute anyway ?
How to shut this keychain prompt off for good?

[Jopp-gh]

I fixed the issue, finally.
The solution was to reset all plugin preferences, build-in and custom.