Use VS Code authentication API to control GitLab accounts

Problem to solve

It's not obvious which GitLab accounts are stored in the extension. We also use custom way to log in and log out.

The only way to see the existing accounts currently is to run GitLab: Remove Account from VS Code command and then see the "accounts to remove" in the quick list:

Proposal

VS Code allows us to create many accounts. This wasn't the case just two years ago. When we do create multiple accounts, we'll have a nice overview called the "Account menu"

We'll use the VS Code authentication API to manage our accounts (they call it sessions)

For detailed investigation and screencasts of the new UI, see the spike result #1217 (comment 1902960104)

Further details

This issue is the last of the Single Account refactor and so we'll also clean up the old multi-account code.

Links / references

added Category:Editor Extensions Editor ExtensionsVS Code devopscreate groupeditor extensions typefeature labels

set weight to 4

added sectiondev label

added to epic gitlab-org/editor-extensions&40

mentioned in issue #1217 (closed)

marked this issue as blocked by #1377 (closed)

marked this issue as blocked by #1378 (closed)

marked this issue as blocked by #1379 (closed)

changed milestone to %Next 1-3 releases

changed milestone to %17.3

added Technical Writing UI text documentation twtriaged labels

mentioned in merge request !1778 (merged)

[error]: Creating `gitlab.com` sessions is no longer supported. It will be implemented again and better in https://gitlab.com/gitlab-org/gitlab-vscode-extension/-/issues/1381
    Error: Creating `gitlab.com` sessions is no longer supported. It will be implemented again and better in https://gitlab.com/gitlab-org/gitlab-vscode-extension/-/issues/1381

So the feature is disabled, and we need to wait for an issue opened 4 months ago and with no recent activities?

EDIT: works when we re authenticate on Gitlab Workflow extension (OAuth Method for me)

Mhm... I think my token has expired and it led me to this issue, any news? @viktomas

I know nothing about coding vs code extensions but I'm willing to contribute

EDIT: Shouldn't this issue be much more active?

@remi.flament1 @G0maa We probably have a bug in the extension. The error you see was never supposed to be shown to people unless they have an extension that depends on GitLab Workflow for authentication.

Do you have such an extension?

If you see this error during day-to-day work with the GitLab Workflow extension, can you please create a new issue and use the bug template with reproduction steps? I might have made a mistake when implementing the feature. If you show me how to reproduce this error locally, I'll try to fix it

---

The extension should work fine if you add an account using the GitLab: Authenticate command.

Thanks for the response @viktomas.

I did authenticate again using GitLab: Authenticate and it worked normally.

The only extension I have (that is related to GitLab) is GitLab Workflow , I'll keep an eye-out if this bug(?) happens again.

Thank you @G0maa Since this is temporarily deprecating the old session management, maybe it's a one-off error that happens when you re-authenticate. However, I wasn't able to reproduce it locally when I tested the change I'd appreciate any additional information.

I received the same error message, leading me to this issue. Restarting the extension, then authenticating, seems to have worked.

I'll try to write some reproducible steps if it happens again on my end

I have the same extension Gitlab Workflow. I use it to create, interact and update my MR. I'm glad this is just a bug, I will try tomorrow at work to re authenticate.

@viktomas I confirm the extension works. I upgraded it and re authenticated with OAuth method.

My token expired, and pressing Re-authenticate caused this alert to appear. An easy fix would be to run the gl.authenticate command instead of calling getSession.

https://gitlab.com/gitlab-org/gitlab-vscode-extension/-/blob/c6e6888366d04cf78f5d9bebc9dc1d045b201724/src/desktop/commands/validate_accounts.ts#L44

mentioned in merge request !2031 (merged)

mentioned in issue gitlab-org/editor-extensions/meta#159 (closed)

mentioned in merge request !2135 (closed)

added gitlab-org#16001 as parent epic

changed milestone to %17.8

mentioned in epic gitlab-org#16001

mentioned in merge request !2214 (closed)

changed weight to 2 from 4

@dashaadu @kisha.mavryck FYI I'm reducing the weight 4 -> 2. I found an approach that significantly reduces the complexity of this feature (in my recent POC (video, MR).

added workflowblocked label

added Next Up label

changed milestone to %Next 1-3 releases

changed milestone to %17.8

mentioned in issue gitlab-org/editor-extensions/meta#188 (closed)

changed milestone to %Next 1-3 releases

assigned to @viktomas

added Technical Roadmap label

added Stretch label

changed milestone to %17.9

Hey @viktomas

• Let's include this issue as a Stretch in Milestone %17.9 per your POC work and suggestion here
• Thank you for the solid POC effort!!!

cc: @dashaadu @tristan.read @elwyn-gitlab @dbernardi

mentioned in issue gitlab-org/editor-extensions/meta#197

changed the description

added workflowin dev label and removed workflowblocked label

mentioned in merge request !2357 (merged)

closed with merge request !2357 (merged)

mentioned in commit 3aa8c648

This issue has been resolved in version 5.39.0

The release is available on:

• GitLab release
• v5.39.0

Your semantic-release bot

2025-02-12 status update

@kisha.mavryck @dashaadu This has been released in 5.39.0. now we are integrated with VS Code Authentication API and the account menu works as expected: