Problem Statement:

As an administrator, I want to be able to use a Service Account to manage my Discovery-Imports to JSM Cloud. 

Summary:

Currently, after setting up the service account, I receive a 403 error when the Discovery Import tries to process data. 

If i switch to use a licensed user with permissions, then the import is successful. Using a service account for this application is logical for capacity and redundancy planning

Steps to Reproduce

1. Configure Assets Discovery
2. Setup Assets Discovery to Export to JSM Cloud
3. Paste the Service Account API token into the Interface
4. Scan your target hosts

Expected Results

After the scan completes, Discovery should be able to upload the results to the linked object schema using the API token in place

Actual Results

The import fails with a HTTP 403 (forbidden) error and the scan is not imported.

[Debug] Calling GetFromJsonAsync for route: https://api.atlassian.com/jsm/assets/workspace/...../v1/import/.....?name=name
4/14/2026 12:46:05 PM: [Error] Error getting data from JSON:
4/14/2026 12:46:05 PM: [Normal] Exceptions:
4/14/2026 12:46:05 PM: [Normal] Response status code does not indicate success: 403 (Forbidden). 

Workaround

Use a licensed account to connect Assets Discovery to JSM Cloud