Bug #25074
closed
Login to different versions of backend on same domain not possible
Added by Marius Muehlberger about 13 years ago.
Updated over 8 years ago.
Category:
Backend User Interface
Description
It seems as if it is not possible to login to different versions of backend (e.g. 4.4.6 and 4.5.0) on the same domain. A restart and cache-cleaning of the browser is required.
It's unusual to use different versions on the same domain, but in our case we use an SSL proxy:
https://ssl-proxy.net/www.typo3-4.4.6-page.com/typo3/
https://ssl-proxy.net/www.typo3-4.5.0-page.com/typo3/
Without a browser-restart it is impossible to login. Backend claims that user or password is wrong. Using an other browser or restarting the used one solves the problem - unless the other backend is called.
(issue imported from #M17638)
Files
In general, working in more backends on the same domain simultaneously is not possible, as this results in a clash of cookie data.
However, it's weird that you can't login two a different installation after logout. I assume, there's a session cookie left, which is not cleared on logout and thus disturbs the login to the next installation.
Can you try to figure out, whether that's really the case? Just use Firebug or a similar tool, to show the remaining cookies after logout and remove them one by one.
Thanks
Steffen
Hello Steffen,
until 4.5.0 it was no issue to have multiple backends opened. The be_typo_user value was stored in a session cookie which is related to the path - so there is no problem. This remains for 4.5.0, so the problem must be somewhere else.
I added a dump of "firecookie". PHPSESSID is not related to this issue as far as I could find out.
I will try to get more details on this issue.
Marius
- Status changed from New to Needs Feedback
- Target version deleted (
0)
- TYPO3 Version set to 4.5
- Is Regression set to No
Hi,
as this issue is very old. Does the problem still exists within newer versions of TYPO3 CMS (6.1.7)?
Hi,thanks for taking care! As far as tested, the problem still exists in 6.1.7.
Currently there is another Bug (#57070) which makes the use of a (single) ssl proxy impossible.
- Category set to Backend User Interface
- Status changed from Needs Feedback to New
- Status changed from New to Needs Feedback
In 6.2 we changed alot in this direction. Does this work for you on latest 6.2 or master?
- Status changed from Needs Feedback to Closed
No feedback within the last 90 days => closing this issue.
If you think that this is the wrong decision or experience this issue again, then please write to the mailing list typo3.teams.bugs with issue number and an explanation or open a new ticket and add a relation to this ticket number.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by