Problem Statement

When a custom domain is added, this triggers the apps' installation lifecycle hook so that they can receive the new base url. 

For Connect on Forge apps, the installation hook will incorrectly receive the Forge oauthClientId as opposed to the Connect oauthClientId, causing subsequent user impersonation requests in the Connect remote to fail.

Workaround

In the meantime, the app vendors can manually generate the correct OAuth client ID for the broken tenants by base64 encoding the following JSON format:

echo -n "{\"hostKey\":\"${TENANT_ID}\",\"addonKey\":\"${ADDON_KEY}\"}" | base64