OAuth authentication fails with VSCode forks (e.g., Kiro IDE) due to hardcoded redirect URI

When attempting to authenticate with the GitLab VS Code extension in a VSCode fork (such as Kiro IDE), OAuth authentication fails with an "invalid redirect URI" error.

Steps to reproduce

  1. Install the GitLab VS Code extension in Kiro IDE (or another VSCode fork)
  2. Run the GitLab: Authenticate command
  3. Select your GitLab instance and choose OAuth authentication
  4. Attempt to authorize the application

Expected behavior

OAuth authentication should succeed and the extension should authenticate with GitLab.

Actual behavior

The browser redirects to GitLab's OAuth authorization page with an "invalid redirect URI" error because kiro://gitlab.gitlab-workflow/authentication is not registered with the OAuth application.

Root cause

The extension's built-in OAuth application is registered with GitLab using only the standard VSCode redirect URI scheme (vscode://). VSCode forks use different URI schemes (e.g., kiro://), which are not authorized.

Possible solutions

  1. Register additional redirect URIs with the OAuth application to support common VSCode forks
  2. Allow users to configure a custom OAuth application with their own redirect URIs
  3. Document the workaround of using Personal Access Token authentication for VSCode forks
Edited by Gordon Shankman