Authentication
The plugin requires authentication to access the GitLab API. You can sign in with OAuth2 (GitLab SaaS only) or with a personal access token (any instance).
OAuth2 (GitLab SaaS)
- When prompted to authenticate, your default browser opens a GitLab authorization page.
- Log in to your GitLab account (if not already logged in) and authorize the plugin.
- After you authorize the plugin, it captures the response through a local callback and stores your credentials automatically. You can then close the browser tab and return to the IDE.
The plugin automatically refreshes your OAuth2 token in the background. If the refresh fails, you will be prompted to re-authenticate.
Completing Authorization Manually
If the local callback cannot be reached (for example, it is blocked by a firewall, or you are signing in on a different machine), select Retrieve Auth Code Manually when prompted. The plugin then guides you through the following steps:
- The authorization link is copied to your clipboard. Paste it into any browser.
- Sign in and authorize the plugin.
- The browser redirects to a
localhostpage that shows an error — this is expected. - Copy the entire URL from the browser's address bar and paste it back into the plugin.
Personal Access Token
You can authenticate with a personal access token on any GitLab instance. This is the only method for self-managed instances, and an alternative to OAuth2 on GitLab SaaS.
- In GitLab, open Edit profile → Access → Personal access tokens.
- Create a token with the api scope.
- Copy the generated token.
- When the plugin prompts for authentication, paste the token.
Changing Account
To switch to a different GitLab account or change the authentication method, use the Change Account action in the GitLab Merge Requests tool window toolbar.
Default Account
When logging in, you can check Use this account for other projects by default. This makes the current credentials the default for any new project that connects to the same GitLab instance.
Credential Storage
All credentials are stored securely in the IDE's built-in credential store (Settings | Appearance & Behavior | System Settings | Passwords). No passwords or tokens are stored in plain text or in project files.