tshirtsgogl.blogg.se - Jira client setup

This begins with a few steps in Airtable that will generate necessary information in order to set up the application link. The general goal of this section is to be able to create an Application Link (App link) on the Jira server. Before proceeding through the steps below, make sure that you have Jira administrator permissions and can log in to Airtable as an admin. This portion of the guide is intended for those individuals who oversee the administrative settings of your organization’s Airtable and Jira accounts. You may wish to restrict Airtable’s access to the following endpoints that are used by Jira Server REST API: Jira Server REST API endpoints are on a separate path from the Jira User interface and login pages. The Airtable sync integration runs in the cloud and needs to make connections from the internet to reach your Jira Server using Atlassian’s REST API. In order to allow Airtable access, while still restricting other external traffic from accessing your Jira Server, add the following static IP addresses to the allowlist in your firewall: If your Jira Server is behind a firewall, then you need to configure your firewall to accept incoming API requests from Airtable. Your Jira Server REST API must be accessible from Airtable. OAuth Troubleshooting Guide: OAuth Signature Rejected.Proxying Atlassian server applications with Apache HTTP Server (mod_proxy_http).Configuring security in the external environment.

Running Jira applications over SSL or HTTPS.

Jira has already built out their own documentation to help guide you through the steps necessary to ensure this is the case for your Jira server: Your Jira Server must be accessible via HTTPS using a certificate issued from a well-known credible certificate authority to ensure a secure connection between Airtable and your Jira Server. You want your DNS server to resolve to one IP for internal traffic and another external IP for external traffic.

Configure your DNS server to resolve the same DNS name for internal and external traffic.

One way to do this is to set up a network load balancer that listens on a particular port and redirect the request to internal IP addresses that internal DNS records point to. For example, if internal DNS resolves to the private IP of the JIRA server within the customer's network, one could create a public DNS record that points to the public IP of the customer’s network firewall.

Add a public DNS record that uses a different DNS name for external traffic.

If your Jira Server’s DNS name resolves to an IP address that is only accessible from a corporate intranet or VPN, you will need to make some DNS modifications. Your Jira Server’s DNS name must resolve to an externally accessible IP address.

To accomplish this goal, there are three overarching steps to complete. The general goal of this portion of the setup process is to allow Airtable systems to securely make API calls against your Jira server instance. This portion of the guide is intended for those individuals who oversee your organization’s network infrastructure. The guide below requires that you or a combination of you and your colleagues have access to modify or set up the various network, Jira and Airtable settings discussed.