When using AdfRenderer from @forge/react to render ADF content that was originally created on a different Confluence page (e.g. a cross-page content reuse pattern as described in https://developer.atlassian.com/platform/forge/using-rich-text-bodied-macros/), media nodes (images/files) fail to render with a 403 JWT authorization error from the Atlassian filestore CDN.
The error occurs because the media token issued by AdfRenderer is scoped to the contentId of the page where the macro is currently running, while the media node belongs to the collection tied to a different page's contentId. The CDN rejects the request as the token does not have read permission for the source page's collection.
Notably, the attachment itself is not page-bound and can be accessed from other pages — the limitation is specific to the JWT token scoping in the AdfRenderer component.

Requested improvement: AdfRenderer should support passing or resolving media tokens for cross-page content, or Atlassian should provide a mechanism for Forge apps to request appropriately scoped media tokens when rendering ADF content sourced from a different page.
Additionally, this limitation should be documented on the ADF media node documentation page so developers are aware