We're running an Outlook add-in and it looks like Microsoft have updated the version of Office.js from 16.00
to 16.01
: outlook:{ios:"16.00",mac:"16.00",web:"16.01",win32:"16.02"}
(via https://appsforoffice.microsoft.com/lib/1.1/hosted/office.js)
One of the changes looks to be additional verification to the abstraction of postMessage
ensuring that the domain (including subdomain) of the child / parent are the same.
Because we host our add-in and central auth server on different subdomains and as a result, all our OAuth flows are broken in Outlook for the web.
outlook-web-16.01.js:18 Failed to execute 'postMessage' on 'DOMWindow': The target origin provided ('https://outlook.domain.com') does not match the recipient window's origin ('https://auth.domain.com')
Outlook on Desktop (both MacOS and Windows) are unaffected.
We already whitelist the domains in our manifest file:
<AppDomains>
<AppDomain>https://outlook.domain.com</AppDomain>
<AppDomain>https://outlook-staging.domain.com</AppDomain>
<AppDomain>https://auth.domain.com</AppDomain>
</AppDomains>
Is it possible to manually specify the version of Office.js that is loaded in each platform so we can upgrade at our own pace and avoid breaking changes like these?