Custom domains

This article explains technical requirements for securing Jira organizations that use a custom domain.

Even if a Jira organization has its own domain configured, proper protection requires adding the instance using the original Atlassian URL.

---

Custom domains

Overview

You can add your Jira organization that uses a custom domain to GitProtect, but you must use its original address instead of the custom one. This limitation results from how Atlassian identifies and authorizes organizations.

Atlassian security and administration APIs are bound to the organization’s original Atlassian-managed URL (for example, yourcompany.atlassian.net), not to the custom domain. The custom domain is mainly a user-facing alias for access and branding.

Internally, Atlassian continues to recognize, authenticate, and grant permissions to the organization only through the original URL registered in Atlassian Administration (https://admin.atlassian.com). As a result, GitProtect must use the original Atlassian URL to correctly:

1. Identify the organization and its applications.

2. Authenticate API requests.

3. Apply security and access controls properly.

Using the custom domain would prevent proper authorization and could lead to failed connections or incomplete protection, which is why the original Atlassian URL is required even when a custom domain is in place.

Finding the original URL

You can find your custom domain's original URL in https://admin.atlassian.com > App URLs > Custom domains > Actions > Show details.

The original URL of your custom domain will be listed under Details section as default URL (fallback).