When signing out in VS code see an unknown username

[adlangx44]

Code of Conduct

• I agree to follow this project's Code of Conduct

On what operating system are you seeing the problem?

Windows (x64)

VS Code version

Seeing the attached message when logging out of the extension. Not sure where it is coming from.

Version of Confluent extension

No response

To Reproduce

1. login to confluent using the extension
2. sign out of the extension using the "Sign out of Confluent Cloud" icon on the extension

Current vs. Expected behavior

Would not expect to see a username I don't recognize.

Relevant log output

Which area(s) are affected? (Select all that apply)

Not sure

Additional context

No response

[adlangx44]

Version of Code

Version: 1.97.2 (user setup)
Commit: e54c774e0add60467559eb0d1e229c6452cf8447
Date: 2025-02-12T23:20:35.343Z
Electron: 32.2.7
ElectronBuildId: 10982180
Chromium: 128.0.6613.186
Node.js: 20.18.1
V8: 12.8.374.38-electron.0
OS: Windows_NT x64 10.0.22631

[shouples]

Thanks for filing this @adlangx44, a couple questions for you:

• Did it load any CCloud resources (environments, Kafka clusters, Schema Registries) after initially signing in?
• Based on that Confluent Cloud item in the Resources view, it doesn't look like it was able to look up your CCloud organization; when you use the same credentials at https://confluent.cloud/, do you see anything like (suspended) in https://confluent.cloud/settings/organizations?

[adlangx44]

"Did it load any CCloud resources (environments, Kafka clusters, Schema Registries) after initially signing in?"

Yes, I was able to see all of our clusters and topics.

"Based on that Confluent Cloud item in the Resources view, it doesn't look like it was able to look up your CCloud organization; when you use the same credentials at https://confluent.cloud/, do you see anything like (suspended) in https://confluent.cloud/settings/organizations?"

I can access cloud normally and no I do not see a suspension

For Context:

I logged in earlier yesterday and left it. I tried some searches and they werent working and I was gonna try again today. When I came back to it today I could no longer see our clusters in the extension so I was trying to figure out how to reauthenticate. I decided to try to the log out icon which is where this message popped.

[shouples]

I logged in earlier yesterday and left it. I tried some searches and they werent working and I was gonna try again today. When I came back to it today I could no longer see our clusters in the extension so I was trying to figure out how to reauthenticate. I decided to try to the log out icon which is where this message popped.

That helps, thanks! It sounds like you ran into the 8-hour CCloud session expiration and were automatically signed out, but it may have hit an issue during that sign-out process.

If you manually # and then sign back out, do you see the same behavior with that unk username?

[adlangx44]

"If you manually # and then sign back out, do you see the same behavior with that unk username?"

I don't. I see my username. I assumed that username is a place holder, but figured I would log the issue in any case.

[shouples]

I don't. I see my username. I assumed that username is a place holder, but figured I would log the issue in any case.

Got it, thank you. I'll dig into it and see if we hit a regression in the session expiration behavior and follow up in this issue with my findings.

[shouples]

@adlangx44 I wasn't able to reproduce the same unk username behavior, but I did see another issue that may have overlap here: #1098

Once that's addressed, we'll see if your issue is still reproducible.