How to list outbound hosts URL in Jira
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
Admins may need to configure specific access for outbound connections from Jira, usually for allowlist or ACL configuration.
This article covers outbound URLs configured in Jira and how to list them.
This article is not definitive — as the products, components and apps evolve in features, there may be more sources to consider.
Treat the information presented here as a good starting point to your investigation rather than a single or definitive source of truth.
These are the outbound hosts Jira itself would reach for (server-to-server). If you're looking for URLs present in contents in Jira (that the end-user Browser would render and access if the link was clicked on), this other article my be useful:
Solution
The outbound connections in Jira are performed to:
Marketplace
Atlassian Analytics
Application Links
WebHooks and Web Requests
Workflows
3rd party apps
All connections are TCP and on ports 443 (when https) or 80 (when http) — unless otherwise explicit in the outbound URL.
Marketplace
Jira relies on https://marketplace.atlassian.com to determine if there are any apps available for upgrade and to check their compatibility to the current version.
If this connection's blocked, some handy features in Jira won't be available but nothing that compromises the end-user — just some extra manual work for Admins when updating or troubleshooting apps malfunctioning.
Atlassian Analytics
Admins may choose to share analytic data with Atlassian to improve the products. These connections are all https to *.atlassian.com.
Application Links
Application Links can be easily listed through the UI on Admin ⚙ > Applications > Integrations / Application links.
WebHooks and Web Requests
Web Requests are Automation for Jira's implementation of WebHooks. They're configured as a Web Request Action in Automation Rules.
The DB query below can list all configured WebHooks and Web Requests matching "http://" or "https://":
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
with webhooks as (
select
'Admin WebHook' as "Type",
"ENABLED" as "Enabled",
"ID" as "Id",
"NAME" as "Name",
"LAST_UPDATED_USER" as "Author",
"URL" as "URL"
from "AO_4AEACD_WEBHOOK_DAO"
),
webrequests as (
select
concat('Automation Rule: ', c."TYPE") as "Type",
case when r."STATE" = 'ENABLED' then true else false end as "Enabled",
r."ID" as "Id",
r."NAME" as "Name",
r."AUTHOR_KEY" as "Author",
c."VALUE" as "URL"
from "AO_589059_RULE_CFG_COMPONENT" c
join "AO_589059_RULE_CONFIG" r on r."ID" = c."RULE_CONFIG_ID"
where (lower(c."VALUE") like lower('%https://%') or lower(c."VALUE") like lower('%http://%'))
)
select * from webhooks union select * from webrequests;For the Automation Web Requests, the whole JSON config will be outputted. You may use database-specific functions to parse just the relevant URL, like this for Postgres (line 18):
1
substring(c."VALUE", '[a-zA-Z]+://[a-zA-Z0-9\.\-\?=_/]+') as "URL"Workflows
Workflows that trigger WebHooks use the same Admin WebHooks already covered here, with no additional URL definition.
There may be, though, 3rd party apps that allow the configuration of URLs directly in their provided Workflow Post-functions or Validators or Conditions. In such case, maybe the query below can be helpful as it queries the Workflows XML descriptors for the "https://" matches:
1
2
3
4
5
6
select
w.id,
w.workflowname,
w.creatorname
from jiraworkflows w
where lower(w.descriptor) like '%https://%';This may result in many false-positives, though. Every Workflow contains a native mention to the workflow descriptor URL (http://www.opensymphony.com/osworkflow/workflow_2_8.dtd) for example.
3rd party apps
Many 3rd party apps (plugins) can also connect to external URL either natively or as configured by the Admins.
If unable to easily assess through each app configs, you'll need to reach out to each app vendor individually for guidance on how to list all URLs the apps connect to or might've been configured to connect to. The URLs may be stored in the database in AO_ tables or maybe elsewhere.
Was this helpful?