MCP: Support custom domains in the OAuth2 site-selection picker

XMLWordPrintable

      Summary:

      When a Cloud site has different custom domains for Jira and Confluence (e.g., jira.company.com and confluence.company.com), the MCP OAuth site picker treats them as separate sites. Since MCP is scoped per site, selecting multiple products fails — even though they share the same Cloud site.

      Suggestion

      The site picker should resolve products by their shared Cloud site ID, not by their custom domain URLs. This way, products with different custom domains are still recognized as one site, and users can select all apps in a single MCP authentication flow.

              Assignee:
              Unassigned
              Reporter:
              Victor Fragoso
              Votes:
              4 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: