Bug #89006
Updated by Helmut Hummel over 4 years ago
There currently are two scenarios where TYPO3 fails to trigger an access denied error and instead triggers a service unavailable error: h2. Szenario 1 * Root page is only accessible for a fe group * A login page below that page is not access protected so that users can log in to view the root page Expectation: When the root page is accessed an access denied error action is triggered, so that an according error handler could for example redirect to a login page Actual behaviour: When the root page is accessed a service unavailable error action is triggered. h2. Szenario 2 * Root page is only accessible for a fe group and extendToSubpages is set * Access to the page (and all pages below) is granted by a SAML SSO authentication mechanism (no login page required, as this happens at the identity provider) Expectation: When the root page is accessed an access denied error action is triggered, so that an according error handler could for example redirect to a login page Actual behaviour: When the root page is accessed a service unavailable error action is triggered.