Issue Summary

Using the PATCH method to submit a schema mapping in a Forge app results in 401

This is reproducible on Data Center: no

Steps to Reproduce

1. Create a Forge app to import third party data into Assets following this guide: https://developer.atlassian.com/platform/forge/assets-import-app/
2. Attempt to modify existing schema mapping using the PATCH endpoint as detailed here: https://developer.atlassian.com/cloud/assets/imports-rest-api-guide/schema-and-mapping/#modifying-an-existing-schema

Expected Results

The schema mapping is updated.

Actual Results

Receive a 401 response with the message

{ "code": 401, "message": "Unauthorized; scope does not match" }

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available