-
Bug
-
Resolution: Fixed
-
Low
-
Minor
Issue Summary
This is reproducible on Data Center: (no)
Installing a connect app using app descriptor in Confluence cloud that has custom domain fails.
And, we get a CORS error like this.
Access to XMLHttpRequest at 'https://$SITENAME.atlassian.net/wiki/rest/plugins/1.0/xxxxxxx' (redirected from 'https://$CUSTOMDOMAIN/wiki/rest/plugins/1.0/pending/xxxxxx') from origin 'https://$CUSTOMDOMAIN' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource.
Steps to Reproduce
- Enable / Configure custom domain for Confluence Cloud
- Install a connect app using its app descriptor
Expected Results
The app should install successfully
Actual Results
The installation fails and we see the following error in browser console.
Access to XMLHttpRequest at 'https://$SITENAME.atlassian.net/wiki/rest/plugins/1.0/xxxxxxx' (redirected from 'https://$CUSTOMDOMAIN/wiki/rest/plugins/1.0/pending/xxxxxx') from origin 'https://$CUSTOMDOMAIN' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource.
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
- relates to
-
CLOUD-6999 Allow custom domains for Cloud apps
- Closed
[MP-236] Installing a connect app using app descriptor in Confluence cloud that has custom domain fails
janis.vanags I believe the broken "getting started" iframe is a slightly different issue (site not redirecting canonical to custom domain when you want it to): see the CAC thread below. It's still unclear exactly to where this was forwarded on the MPAC team or if it was ever logged. https://community.atlassian.com/t5/Confluence-Custom-Domains-EAP/Update-on-known-issues-and-planned-GA-timing/m-p/2722879#M8
The install-apps-on-custom-domains feature (which is effectively caused by the site redirecting from canonical to custom domain when you don't want it to) was broken in atlassian-connect-express until I fixed it in this PR, with the MPAC upload request being sent to one hostname but the followup URL polling being redirected to a different host and thus losing cookies in the process. Add browser CORS and I can imagine why this problem exists here too. https://bitbucket.org/atlassian/atlassian-connect-express/pull-requests/465/fix-installation-errors-on-sites-with
I was referred to here from ECOHELP-45457. This presumably is related to broken "Getting started" iframe for all apps installed on Confluence with custom domain.
I can confirm it is fixed now. Thank you!