Local Network Access Checks in Chrome Prevent Setting up GitLab for Jira Cloud app on Self-Managed instance within local IP range

Summary

Customers cannot set up the GitLab for Jira Cloud app with self-managed GitLab instances that are in a local IP range when using Chrome/Chromium-based browsers due to Chrome's Local Network Access (LNA) prompts introduced in Chrome 142.

Allowing "Local Network Access" within site settings for the self-managed instance, atlassian, and GitLab.com does not change behavior. Even with all three set to "allow" the set up fails.

Setting up the integration in Firefox is the current workaround.

Link to chrome blog post on the new feature: https://developer.chrome.com/blog/local-network-access

What is the current bug behavior?

When setting up the GitLab for Jira Cloud integration, the integration creates a "Failed to load Jira Connect Application ID. Please try again" error when trying to sign into a self-managed GitLab instance. As a result the integration cannot be set up in google chrome.

What is the expected correct behavior?

Integration is able to be set up without error.

Relevant logs and/or screenshots

# Sampled from HAR file:

      {
        "_initiator": {
          "type": "preflight",
          "url": "https://<gitlab_url>/-/jira_connect/oauth_application_id",
        },
        "_priority": "High",
        "_resourceType": "preflight",
        "cache": {},
        "request": {
          "method": "OPTIONS",
          "url": "https://<gitlab_url>/-/jira_connect/oauth_application_id",
          "httpVersion": "",
          "headers": [
            {
              "name": "Accept",
              "value": "*/*"
            },
            {
              "name": "Access-Control-Request-Headers",
              "value": "x-csrf-token,x-requested-with"
            },
            {
              "name": "Access-Control-Request-Method",
              "value": "GET"
            },
            {
              "name": "Origin",
              "value": "https://gitlab.com"
            },
            {
              "name": "Sec-Fetch-Mode",
              "value": "cors"
            }
          ],
...
        },
        "response": {
          "status": 0,
...
          "_error": "net::ERR_BLOCKED_BY_PRIVATE_NETWORK_ACCESS_CHECKS",

Patch release information for backports

If the bug fix needs to be backported in a patch release to a version under the maintenance policy, please follow the steps on the patch release runbook for GitLab engineers.

Refer to the internal "Release Information" dashboard for information about the next patch release, including the targeted versions, expected release date, and current status.

High-severity bug remediation

To remediate high-severity issues requiring an internal release for single-tenant SaaS instances, refer to the internal release process for engineers.