Sabbir Ahmmed
04/14/2026, 11:35 AM026-04-14 13:28:58 info
2026-04-14 13:28:58 info ----- START CHECK -----
2026-04-14 13:28:58 info
2026-04-14 13:29:01 info Connector exited, processing output
2026-04-14 13:29:01 info Output file jobOutput.json found
2026-04-14 13:29:01 info Connector exited with exit code 0
2026-04-14 13:29:01 info Reading messages from protocol version 0.2.0
2026-04-14 13:29:02 error 'GET' request to '<https://api.atlassian.com/ex/jira/REMOVED/rest/api/3/users/search?maxResults=50>' failed with status code '401' and error message: 'Unauthorized; scope does not match'. Request (body): 'None'. Response (body): '{'code': 401, 'message': 'Unauthorized; scope does not match'}'. Response (headers): '{'Content-Type': 'application/json', 'Content-Length': '59', 'Connection': 'keep-alive', 'Date': 'Tue, 14 Apr 2026 11:29:01 GMT', 'X-Trace-Id': '70c79aeb7ce845b0a956298a0020bd68', 'X-Failure-Category': 'FAILURE_CLIENT_SCOPE_CHECK', 'X-Frame-Options': 'SameOrigin', 'X-Content-Type-Options': 'nosniff', 'X-Xss-Protection': '1; mode=block', 'Atl-Traceid': '70c79aeb7ce845b0a956298a0020bd68', 'Atl-Request-Id': '70c79aeb-7ce8-45b0-a956-298a0020bd68', 'Strict-Transport-Security': 'max-age=63072000; preload', 'Report-To': '{"endpoints": [{"url": "<https://dz8aopenkvv6s.cloudfront.net>"}], "group": "endpoint-1", "include_subdomains": true, "max_age": 600}', 'Nel': '{"failure_fraction": 0.01, "include_subdomains": true, "max_age": 600, "report_to": "endpoint-1"}', 'Server-Timing': 'atl-edge;dur=12,atl-edge-internal;dur=2,atl-edge-upstream;dur=10,atl-edge-pop;desc="aws-eu-central-1"', 'Server': 'AtlassianEdge', 'X-Cache': 'Error from cloudfront', 'Via': '1.1 e82859bd3e5e584a3698e67f22415dae.cloudfront.net (CloudFront)', 'X-Amz-Cf-Pop': 'FRA60-P13', 'X-Amz-Cf-Id': 'vly1H8ul5L3q19yPPZmPVZsjpixui7fPfBa4YC5MeFVj4Gp_2vqxbQ=='}'.
2026-04-14 13:29:02 warn Stream users is not available: HTTP Status Code: 401. Error: Unauthorized. Please ensure you are authenticated correctly.
2026-04-14 13:29:02 error Check failed
2026-04-14 13:29:02 info Checking for optional control message...
2026-04-14 13:29:02 info Optional control message not found. Skipping...
2026-04-14 13:29:02 info Writing output of 68e63de2-bb83-4c7e-93fa-a8a9051e3993_87f91e60-73ec-4176-8c3b-67b155871d15_0_check to the doc store
2026-04-14 13:29:02 info Marking workload 68e63de2-bb83-4c7e-93fa-a8a9051e3993_87f91e60-73ec-4176-8c3b-67b155871d15_0_check as successful
2026-04-14 13:29:02 info
2026-04-14 13:29:02 info Deliberately exiting process with code 0.
2026-04-14 13:29:02 info ----- END CHECK -----kapa.ai
04/14/2026, 11:35 AM'Unauthorized; scope does not match'
X-Failure-Category: FAILURE_CLIENT_SCOPE_CHECK
This means your OAuth token (used via the Atlassian OAuth 3LO flow) does not have the required scopes to access the Jira Users API (/rest/api/3/users/search). What's happening The Jira connector is trying to check the users stream during the connection check, but the OAuth token you've provided lacks the necessary permission scopes. [Jira source docs] How to fix it The required OAuth scopes for the Jira connector include read:jira-user (among others). Based on the PR that added OAuth 2.0 support to source-jira, the full set of required scopes is: [OAuth support PR]
• read:jira-work
• read:jira-user
• offline_access
• read:board-scope:jira-software
• read:sprint:jira-software
Steps to resolve:
1. Go to your Atlassian Developer Console and find the OAuth app you're using.
2. Ensure all the required scopes listed above are granted to the app.
3. Re-authorize the connection so a new token with the correct scopes is issued.
4. Re-test the Jira source connection in Airbyte.
Alternatively, if you prefer to avoid OAuth complexity, you can use API Token authentication instead, which requires only your Atlassian account email and an API token generated from https://id.atlassian.com/manage-profile/security/api-tokens. [Jira setup guide] 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.