TYPO3 Core

I investigated this and found that the steps to reproduce are wrong.

correct is:

1. Have a site running on 4.2.
2. be shure that there are tempCACHE* files in typo3conf/ don't delete them
3. Update the source to the latest 4.3/trunk.
4. Perform a DB update DONT'T run the update wizard.
5. Try to login to the BE.

this shows already the solution:
clearing the cache files will do the trick.
(it seems that this was not needed in earlier versions)

to ease live of admins I suggest to add the attached patch which adds "did you clear the tempCACHE* files after updating your site?" to the "no auth methods..." popup.

I do have a site running on TYPO3 4.3 now but nothing of this helped. Neither deleting temp_CACHE* files nor performing or not performing update wizards and db updates, i tried it several times all the way round but i couldn’t get it to work…
Also I went through almost the whole internet and tried eerything it was told to me in forums, nothing helped.
Additionally, i changed login procedure in localconf.php to rsa and added rsaauth to the extension list, then, the following happened: i didn’t get an error but if i sent the login data it loads something and then shows an empty loginform…
seems to be hard to fix…

Same situation on my T3 installation.

I could fix it by install/loading the latest version of extension 'TYPO3 System Services' (sv 1.1.0).
In my case an older version was located in typo3conf/ext and loaded as "Local" version (same version number). The latest 'sv' brings new files and configurations but couldn't be loaded because the "Local" version takes precedence (Double installs!)

How to fix:

- delete extensionfolder 'sv' from typo3conf/ext/
- delete temp_CACHE* files

Can we close this issue? The loginSecurityLevel has been set already, so it's not really an issue in the core anymore.

Hi Benni, since this bug also was about having an empty field for loginSecurityLevel in the Install Tool, I think this bug partly is still there:

If you don't have a value set for loginSecurityLevel in localconf.php, the Install Tool shows an empty field there.

For other values, which you did not set in localconf.php either, the standard value IS displayed inside the according field.

I think this should still be fixed.

Hi - just updated 4.2.2 to 4.4.2 and have received message: "No authentication methods available. Please, contact your TYPO3 administrator." when logging into backend. Deleting temp_CACHE* didn't work. Nor did setting loginSecurityLevel in the install section. No sv in local extensions. This bug appears to be alive still.

Hey - So did I. And not one of the promissed solutions did work for me, too..

The problem occured in a typo3-install of mine after an upgrade to PHP 5.3.2. Afterwards i downgraded to 5.2.11, everything is working fine now.