[BUG]: #1560778826: You are not authenticated to see this view

[agendartobias]

TYPO3 v12.4.15 luxletter v26.2.0 (same on v26.1.0)

I am adding a new newsletter, select a page and get this error instead of a preview:

Core: Exception handler (WEB): Uncaught TYPO3 Exception: #1560778826: You are not authenticated to see this view | In2code\Luxletter\Exception\AuthenticationFailedException thrown in file /var/www/html/typo3conf/ext/luxletter/Classes/Controller/FrontendController.php in line 76. Requested URL: https://mysite.si/enovice/preview.html?tx_luxletter_preview%5Blanguage%5D=0&tx_luxletter_preview%5Blayout%5D=NewsletterContainer&tx_luxletter_preview%5Borigin%5D=127

In Extension Configuration -> luxletter if i remove checkbox in Multilanguage mode and define URL by myself: https://mydomain.si/enovice?type=1562349004 preview works ok

[einpraegsam]

I can confirm this issue if the preview domain is different to the domain where the backend user is logged in into backend. As long as it is possible to login into backend with another domain this is more a missing feature at the moment.

---

Problem: There is a simple check that is called before initializePreviewAction() is called if the requested user is logged in into backend.

[agendartobias]

Hey this is strange because my domain is the same. Maybe it has something to do that we have Varnish cache on FE?

[linawolf]

I can confirm, I have this error also in an installation where preview domain backend domain are the same. we do not have a Varnish cache

[linawolf]

• Downgrading in2code/luxletter (26.2.0 => 25.0.4)

Resolved the problem for me

[einpraegsam]

We are currently working on the TYPO3 12/13 update for LUXletter. While digging into the code I just stumbled over https://github.com/in2code-de/luxletter/blob/develop/Classes/Domain/Service/PreviewUrlService.php#L90 - can someone please comment out line 90-92 (so function getUrlFromPageIdentifier() is not used any more) and give me feedback if this fixes the problem?

[einpraegsam]

This issue should be solved

[julianhofmann]

We also recently had a case where we encountered this exception. The reason for this was a multi-domain instance in which the BE login was under a domain different from the newsletter page. Accordingly, the BE session is for the “wrong” domain and the user is not authenticated.

It is not necessary to reopen the issue. However, this note may help others to troubleshoot the problem.

(Maybe, the message of the AuthenticationFailedException could be extended by this information)