if you use the user's browser to generate the PDF (instead of the headless Chrome Docker container)
if the URL used to access XWiki is the same for the user's browser and the headless Chrome, i.e. if the "XWiki URI" PDF export configuration has been modified, and its value matches the URL that the user's browser is using. The reason is that the session cookie we pass to Chrome is bound to the URL that was used to create that session cookie. If the URL changes, the session cookie is not valid anymore, so authentication has to be restored from the other authentication cookies (username and password) which are IP-bound. The session cookie doesn't seem to be IP-bound from my tests
guest users have read access, BUT, even if the PDF export doesn't fail in this case, the generated PDF might not be complete, because the user is not authenticated when the PDF is generated
This message was sent by Atlassian Jira (v9.3.0#930000-sha1:287aeb6)
If image attachments aren't displayed, see this article.