This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 2%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMD%3C/text%3E%3C/svg%3E)
Hello,
I'm currently in the process of setting up a SharePoint 2019 web app with cross site publishing. Currently I have one publishing site and three authoring sites.
I am currently working my display templates and trying to get a download document option working.
I'm attempting to use the following URL to achieve this:
But receive an error "Sorry, something went wrong. An unexpected error occurred.
If I set the download link to be "https://authoring_site1.company.com/Document_Library/test.pdf" I am prompted to log into the other site collection and then the file downloads.
The only work around I have found so far is to enable anonymous access on the Document Library on the authoring site, but this probably isn't a great option with information security in mind.
I am currently looking into this issue and will give you an update as soon as possible.
Thank you for your understanding and support.
if links to these documents appear on public site (i.e. site which is accessible by anonymous users) then probably anonymous users should also be able to see content of these documents? If so then there is no problem with enabling of Anonymous access to your authoring catalog doclib. Content creators should clearly understand that though.
The public/publishing site does not allow anonymous access, users will be prompted for login to gain access. And with anonymous access on the authoring site libraries download links could be shared anonymously which we can't really allow.
ah, ok - so your publishing sites don't allow anonymous access (as well as authoring site). So basically you need SSO between publishing and authoring sites so users won't need to login again when going to authoring site after clicking on the file link. Probably you should look at solution described here: SSO between 2 host-named sitecollections with different subdomains. It is for host-header site collection but with different sub domains like in your case.