Hello,

I just stumbled accross a really interesting problem in my 404 page implementation and spoke about it directly with Kevin Dejour from eZ who told me to create this issue.

I wanted to override the exceptions pages (with the native Symfony system, https://symfony.com/doc/3.4/controller/error_pages.html), and tried it with a simple template override as well as with a custom controller. In both cases, whenever I try to use anything linked to eZ in my template/controller, I get the following exception: “The token storage contains no authentication token”.

One person on the eZ slack had the same issue and fixed it with what I'd call bruteforcing (the end of his thread is here : https://ezcommunity.slack.com/archives/C3YFR5ZM4/p1533052591000067) but I think that on his diagnostic of the problem, he has a point.

Why do eZ generates its token after the Exceptions handler? Would it be possible to have a full management of the exceptions pages with Platform (which is, in my experience, an important feature) without having to shunt down/bypass the Symfony firewall.