Bug #23354
closed
Switch-back user mode: Login refresh problem
0%
Description
When you're logged in as an admin and switch to another backend user in switch-back mode, TYPO3 asks for the password of this user once the login must be refreshed. So the only possibility is to log out and login again as you normally don't know every user's password.
(issue imported from #M15356)
Files
Updated by Oliver Hader over 13 years ago
Can you please provide the exact version of TYPO3 you used to have that behaviour? Did it work in a previous version or in other words "is it another regression"?
Updated by over 13 years ago
It's no regression as far as I can tell.
In TYPO3 <= 4.3 once the session has expired there is a popup window allowing relogin. If I logged in as "admin" and changed to user "editor" in switch-back mode, the popup suggests "editor" as username. But there I can change username to "admin" and enter the admin password and so I stay logged in.
In TYPO3 4.4+ login refresh is done by ExtJS. Now if I am logged in as "admin" and change to user "editor" in switch-back mode, the popup doesn't let me choose the username (see screenshot), so as I don't know the password from user "editor", I cannot stay logged in.
Updated by Alexander Opitz over 10 years ago
- Category set to Backend User Interface
- Target version deleted (
0) - Is Regression set to No
Updated by Mathias Schreiber about 9 years ago
- Target version set to 7.4 (Backend)
I'm targetting this one for 7.4, but still I'm not sure if there is something to fix.
Switching into a user is a temporary action and thus should not do magic of some sorts.
Updated by Riccardo De Contardi over 8 years ago
still present in both 6.2.14 and 7.4 (latest master)
Updated by Susanne Moog over 8 years ago
- Target version changed from 7.4 (Backend) to 7.5
Updated by 
Updated by Riccardo De Contardi about 7 years ago
Still present on 8.7-dev (latest master)
Updated by Josef Glatz over 6 years ago
- TYPO3 Version changed from 4.4 to 8
- PHP Version changed from 5.2 to 7.0
can confirm, therefore update issue versions
Updated by Christian Kuhn over 6 years ago
- Status changed from New to Closed
since 'switch to user' is meant as a temporary test from an admin side, and with the default session timeout being increased to many more hours meanwhile, i don't consider this issue to me relevant to be solved anymore at the moment. i'll close it for now. please feel free to re-open the issue with more description on a possible solution for at least core version v9 if you still feel this should be tackled.