Skip to content

fix: Always offer to run Authenticate command when token expires

Lennard Sprong requested to merge gitlab-community/gitlab-vscode-extension:X_Sheep/reauthenticate into main
  • Please check this box if this contribution uses AI-generated content (including content generated by GitLab Duo features) as outlined in the GitLab DCO & CLA. As a benefit of being a GitLab Community Contributor, you can request access to GitLab Duo.

Description

When an OAuth token expires, the Re-authenticate button attempted to make a new Session, which is deprecated in the GitLab Workflow extension.

This change will start the regular Authenticate command, which will prompt the user to make a new OAuth or PAT session. This will apply to both expired PAT and expired OAuth sessions.

Related Issues

This is related to the user comments of #1381, but not a fix of the issue described in the original post. This will cause less users to be directed to this issue page.

How has this been tested?

One way to test this is to make a Personal Access Token in GitLab, use it to log into the extension, and then revoke it on GitLab. Reopening the folder in VS Code will cause the validation to fail and the prompt to Re-authenticate to appear.

Screenshots (if appropriate)

image

The error that appeared when trying to re-authenticate

What CHANGELOG entry will this MR create?

  • fix: Bug fix fixes - a user-facing issue in production - included in changelog
  • feature: New feature - a user-facing change which adds functionality - included in changelog
  • BREAKING CHANGE: (fix or feature that would cause existing functionality to change) - should bump major version, mentioned in the changelog
  • None - other non-user-facing changes
Edited by 🤖 GitLab Bot 🤖

Merge request reports