doc/administration/settings/editor_extensions.md
{{< details >}}
{{< /details >}}
Configure editor extensions settings for your GitLab instance.
{{< history >}}
{{< /history >}}
You can configure editor extensions to connect and authenticate with GitLab using an OAuth application ID. The configuration steps differ depending on your IDE.
To create an OAuth application for VS Code:
vscode://gitlab.gitlab-workflow/authentication.
api scope.gitlab.authentication.oauthClientIds setting in your VS Code configuration.To create an OAuth application for JetBrains IDEs:
http://127.0.0.1/api/oauth/gitlab/authorization.api scope.{{< history >}}
enforce_language_server_version. Disabled by default.{{< /history >}}
[!flag] On GitLab Self-Managed, by default this feature is not available. To make it available, an administrator can enable the feature flag named
enforce_language_server_version. On GitLab.com, this feature is available but can be configured by GitLab.com administrators only. On GitLab Dedicated, this feature is available.
By default, any GitLab Language Server version can connect to your GitLab instance when personal access tokens are enabled. To block requests from clients on older versions, configure a minimum language server version. Clients older than the minimum allowed Language Server version receive an API error.
Prerequisites:
You must be an administrator.
# For a specific user
Feature.enable(:enforce_language_server_version, User.find(1))
# For this GitLab instance
Feature.enable(:enforce_language_server_version)
To enforce a minimum GitLab Language Server version:
To allow any GitLab Language Server clients:
[!note] Allowing all requests is not recommended. It can cause incompatibility if your GitLab version is ahead of your extension version. You should update your extensions to receive the latest feature improvements, bug fixes, and security fixes.