Query around External Backend access

Forge
1

Hi, I’ve few queries around external backend URL access setup in Forge app manifest file.
Below is my current implementation and my query

Intention: Jira User / Admin fills up a form where they enter their ACCELQ(External System) credentials to establish connection between Jira and ACCELQ to allow REST API calls to hit ACCELQ server.

Now we have two kinds of ACCELQ servers - On Cloud whose URL is *.accelq.io and On Premise URL where client have full control over domain name (*)

So the question is will Forge allow setting up star as the value under external → fetch → backend. If not, then what are other options?
```
permissions:

scopes:

- read:jira-work

- write:jira-work

- read:jira-user

- manage:jira-configuration

- storage:app

external:

fetch:

backend:

    - '\*.accelq.io'

    - '\*.ngrok-free.app'

```

2

Hi Vivek,

Yes you can wildcard the subdomain (Examples: https://developer.atlassian.com/platform/forge/manifest-reference/permissions/#fetch)

You will need to update your manifest to align with:
**backend:

  • *.accelq.io**

Cheers
Ben

3

Can I do just “*”. That would save us from re-uploading the app whenever we onboard a new on premise client? Because we cannot enforce clients on their on-premise domain urls.

4

Hi Vivek, yes that is valid but some customers may have issue with that.

Another option is to use the upcoming feature - https://developer.atlassian.com/platform/forge/customer-managed-egress-and-remotes/ which lets your customers to define the available remote. You can subscribe to the change log for updates on when that will launch: https://developer.atlassian.com/platform/forge/changelog/

Cheers
Ben