Issue Feature Accepted Orphaned

#86549Allow Backend URL to be specified for Admin Panel

Xavier Perseguers 10/02/18, 21:48 updated 03/24/20, 11:26

Description

This feature request is related to #86548

Imagine you have a multi-domain install:

  • domain1.example.com
  • domain2.example.com
  • domain3.example.com

You want (for whichever – good – reason) to force (or at least highly suggest) the webmasters to access the Backend through admin.example.com.

In order for Admin Panel to work, the trick is to force the FE/BE cookies like that (typically in AdditionalConfiguration.php):

$GLOBALS['TYPO3_CONF_VARS']['BE']['cookieDomain'] = '.example.com';
$GLOBALS['TYPO3_CONF_VARS']['FE']['cookieDomain'] = '.example.com';

This will effectively allow the Admin Panel to show up whenever you are authenticated into the Backend (on admin.example.com) while browsing, say, domain1.example.com.

So far so good!

However then try to click on the admin panel button to edit the page:

admin.png

The Backend will open up but using domain1.example.com/typo3 and not admin.example.com/admin (because there is no such configurable setting).

Note: the jump link is generated in typo3/sysext/frontend/Classes/View/AdminPanelView.php around line 654 and generates an absolute link starting with a / (slash), thus effectively reusing the current domain. Trying to hardcode (to test) some scheme + domain at this place won’t work since the security token will not be correct.

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.

Fix this issue

Start the commit message of your patch with this. Add what the patch does, and the versions it goes to in "Releases:". How to create a patch

Commit message
[FEATURE] Allow Backend URL to be specified for Admin Panel Resolves: #86549 Releases: main