Hi all,
We have a Connect application that sends some information to Jira DevInfo API – /rest/devinfo/0.10/bulk. The information is sent from our backend Java application using JWT.
All worked well for the Connect app.
We adopted Forge from the Connect application according to this instruction – How to adopt Forge from Connect
There were no errors during Forge manifest creation, neither during forge deploy & forge install.
The adopted application seems to work well, except that the backend part now is unable to send DevInfo data to Jira:
POST https://dmalyshkin-gk.atlassian.net/rest/devinfo/0.10/bulk
HTTP/1.1 403 Forbidden
Response headers: [name: Date, value: Fri, 14 Mar 2025 07:51:45 GMT], [name: Content-Type, value: text/html;charset=UTF-8], [name: Server, value: AtlassianEdge], [name: Timing-Allow-Origin, value: *], [name: X-Arequestid, value: 244b8a07a835ee031a3100e2b7fea5c5], [name: X-Aaccountid, value: 712020%3A4e2b3161-a842-4079-a7a6-bea75d2e6510], [name: Cache-Control, value: no-cache, no-store, no-transform], [name: X-Content-Type-Options, value: nosniff], [name: X-Xss-Protection, value: 1; mode=block], [name: Atl-Traceid, value: 1a5c63cf5ebd4bceb43b3dad27454cda], [name: Atl-Request-Id, value: 1a5c63cf-5ebd-4bce-b43b-3dad27454cda], [name: Strict-Transport-Security, value: max-age=63072000; includeSubDomains; preload], [name: Report-To, value: {"endpoints": [{"url": "https://dz8aopenkvv6s.cloudfront.net"}], "group": "endpoint-1", "include_subdomains": true, "max_age": 600}], [name: Nel, value: {"failure_fraction": 0.001, "include_subdomains": true, "max_age": 600, "report_to": "endpoint-1"}], [name: Server-Timing, value: atl-edge;dur=277,atl-edge-internal;dur=13,atl-edge-upstream;dur=265,atl-edge-pop;desc="aws-us-east-1"], [name: Transfer-Encoding, value: chunked]
Permissions in the manifest are:
permissions:
scopes:
- read:connect-jira
- write:connect-jira
- act-as-user:connect-jira
- delete:connect-jira
- access-email-addresses:connect-jira
What do we do wrong?