Issue Summary

This is reproducible on Data Center: (no)

Connect macros fails to render if using "admin key" feature.

This happens if the connect app/macro is making API calls or permission checks that require the user to have specific permissions on the page.
When using "admin key" features, admins can gain access to the page but, because of how connect JWT and "admin key" feature works, the admin user may not have the right level of permission to render the macros properly. For example,

• The macro app is making API calls asUser that is fails - and macro cannot load without the content body.
• The macro app performs a permissions check against the content - which fails as "admin key" doesn't update permissions of the content.

Steps to Reproduce

1. Create a Connect macro that makes asUser API calls to get content body then renders/displays it.
2. Install the connect app
3. As user1 create a restricted page and add the macro and publish the page
4. As user2, who is a site-admin, use "admin key" feature the access the page

Expected Results

The macro should render properly

Actual Results

The page loads, but the 3rd party macro fails to render

Workaround

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