#108709Inconsistent Log Format and Duplicate Entries for authentication processes
Description
The Log format of the components TYPO3.CMS.Core.Authentication.AuthenticationService and TYPO3.CMS.Core.Authentication.BackendUserAuthentication is inconsistent. The AuthenticationService does not add JSON data for successful authentications and invalid passwords. For the invalid password, a massage is added instead. While the BackendUserAuthentication always adds JSON data. For the case a not existing user is given, the AuthenticationService is adding JSON data, but the IP key is different to the others.
In case of a successful Backend login with a local backend user, the event is written to the log twice. Once by the component TYPO3.CMS.Core.Authentication.AuthenticationService and once by TYPO3.CMS.Core.Authentication.BackendUserAuthentication. This could be linked to the task: https://forge.typo3.org/issues/108564
In the following Log data, the user localadmin is a backend user. While the user my_user is an LDAP user. For the LDAP authentication, the “causal/ig_ldap_sso_auth” extension is used.
Mon, 19 Jan 2026 08:17:09 +0000 [NOTICE] request="ad54cc0c14dde" component="TYPO3.CMS.Core.Authentication.AuthenticationService": BE Authentication successful for username 'localadmin'
Mon, 19 Jan 2026 08:17:09 +0000 [INFO] request="ad54cc0c14dde" component="TYPO3.CMS.Core.Authentication.BackendUserAuthentication": User localadmin logged in from 172.19.0.1 - {"username":"localadmin","ip":"172.19.0.1"}
Mon, 19 Jan 2026 08:17:35 +0000 [INFO] request="8d2b8c3902a1b" component="TYPO3.CMS.Core.Authentication.AuthenticationService": Login-attempt from username "localadmin1" not found! - {"username":"localadmin1","REMOTE_ADDR":"172.19.0.1"}
Mon, 19 Jan 2026 08:18:01 +0000 [NOTICE] request="12bf5f4fe035f" component="TYPO3.CMS.Core.Authentication.AuthenticationService": Login-attempt from 172.19.0.1, username 'my_user', password not accepted!
Mon, 19 Jan 2026 08:18:28 +0000 [INFO] request="c2a6169542078" component="TYPO3.CMS.Core.Authentication.BackendUserAuthentication": User my_user logged in from 172.19.0.1 - {"username":"my_user","ip":"172.19.0.1"}
Mon, 19 Jan 2026 09:27:44 +0000 [NOTICE] request="17bd5af79a69d" component="TYPO3.CMS.Core.Authentication.AuthenticationService": BE Authentication successful for username 'localadmin'
Mon, 19 Jan 2026 09:27:44 +0000 [INFO] request="17bd5af79a69d" component="TYPO3.CMS.Core.Authentication.BackendUserAuthentication": User localadmin logged in from 172.19.0.1 - {"username":"localadmin","ip":"172.19.0.1"}
Mon, 19 Jan 2026 09:29:38 +0000 [NOTICE] request="4aee5f8dd7bd1" component="TYPO3.CMS.Core.Authentication.AuthenticationService": Login-attempt from 172.19.0.1, username 'localadmin', password not accepted!
Mon, 19 Jan 2026 09:30:58 +0000 [INFO] request="fb68602f10dd4" component="TYPO3.CMS.Core.Authentication.BackendUserAuthentication": User localadmin logged in from 172.19.0.1 - {"username":"localadmin","ip":"172.19.0.1"}
Mon, 19 Jan 2026 09:34:09 +0000 [INFO] request="612ff9bf61761" component="TYPO3.CMS.Core.Authentication.BackendUserAuthentication": User localadmin logged in from 172.19.0.1 - {"username":"localadmin","ip":"172.19.0.1"}
Mon, 19 Jan 2026 09:36:27 +0000 [NOTICE] request="17a635e7f254b" component="TYPO3.CMS.Core.Authentication.AuthenticationService": Login-attempt from 172.19.0.1, username 'localadmin', password not accepted!
Mon, 19 Jan 2026 09:36:40 +0000 [NOTICE] request="e99a33a40d7a6" component="TYPO3.CMS.Core.Authentication.AuthenticationService": BE Authentication successful for username 'localadmin'
Mon, 19 Jan 2026 09:36:40 +0000 [INFO] request="e99a33a40d7a6" component="TYPO3.CMS.Core.Authentication.BackendUserAuthentication": User localadmin logged in from 172.19.0.1 - {"username":"localadmin","ip":"172.19.0.1"}
Mon, 19 Jan 2026 09:39:00 +0000 [NOTICE] request="9cb6ccec61171" component="TYPO3.CMS.Core.Authentication.AuthenticationService": Login-attempt from 172.19.0.1, username 'localadmin', password not accepted!
The log configuration in the settings.php is:
'LOG' => ['TYPO3' => ['CMS' => ['Core' => ['Authentication' => [
'BackendUserAuthentication' => [
'writerConfiguration' => [
'writerConfiguration' => [
\TYPO3\CMS\Core\Log\LogLevel::INFO => [
\TYPO3\CMS\Core\Log\Writer\FileWriter::class => [
'logFile' => \TYPO3\CMS\Core\Core\Environment::getVarPath() . '/log/typo3_authentication.log',
],
],
],
],
'AuthenticationService' => [
'writerConfiguration' => [
\TYPO3\CMS\Core\Log\LogLevel::INFO => [
\TYPO3\CMS\Core\Log\Writer\FileWriter::class => [
'logFile' => \TYPO3\CMS\Core\Core\Environment::getVarPath() . '/log/typo3_authentication.log',
],
],
],
],
],
],],],],]Reviews 2
History 710
-
Markus Klein changed description <span data-processor="relativetime" data-value="2026-01-21T13:26:59+00:00" > 01/21/26, 13:26 </span>
-
Markus Klein changed description <span data-processor="relativetime" data-value="2026-01-21T13:31:23+00:00" > 01/21/26, 13:31 </span>
-
Tob Mit commented <span data-processor="relativetime" data-value="2026-01-21T13:40:15+00:00" > 01/21/26, 13:40 </span>
Actually, two points were missing in that configuration. Here is the complete log configuration i use. Thank you for the formatting btw.
'LOG' => [ 'TYPO3' => [ 'CMS' => [ 'Core' => [ 'Authentication' => [ 'BackendUserAuthentication' => [ 'writerConfiguration' => [ \TYPO3\CMS\Core\Log\LogLevel::INFO => [ \TYPO3\CMS\Core\Log\Writer\FileWriter::class => [ 'logFile' => \TYPO3\CMS\Core\Core\Environment::getVarPath() . '/log/typo3_authentication.log' ], ], ], ], 'AuthenticationService' => [ 'writerConfiguration' => [ \TYPO3\CMS\Core\Log\LogLevel::INFO => [ \TYPO3\CMS\Core\Log\Writer\FileWriter::class => [ 'logFile' => \TYPO3\CMS\Core\Core\Environment::getVarPath() . '/log/typo3_authentication.log', ], ], ], ], ], ], 'deprecations' => [ 'writerConfiguration' => [ 'notice' => [ 'TYPO3\CMS\Core\Log\Writer\FileWriter' => [ 'disabled' => false, ], ], ], ], ], ], 'writerConfiguration' => [ \TYPO3\CMS\Core\Log\LogLevel::INFO => [ \TYPO3\CMS\Core\Log\Writer\FileWriter::class => [ 'logFile' => \TYPO3\CMS\Core\Core\Environment::getVarPath() . '/log/typo3_info.log' ], ], ], ], -
Gerrit Code Review pushed patch set 1 for main to change 96944 status
NewUnder Review <span data-processor="relativetime" data-value="2026-10-20T16:17:29+00:00" > 10/20/26, 16:17 </span> -
Markus Klein commented and changed assigned to Markus Klein <span data-processor="relativetime" data-value="2026-10-20T16:19:33+00:00" > 10/20/26, 16:19 </span>
@wat12luj Please test the change linked above, if this fits your needs.
-
Gerrit Code Review pushed patch set 2 for main to change 96944 <span data-processor="relativetime" data-value="2026-10-21T19:37:49+00:00" > 10/21/26, 19:37 </span>
-
Gerrit Code Review pushed patch set 1 for 14.3 to change 96990 <span data-processor="relativetime" data-value="2026-10-22T08:20:22+00:00" > 10/22/26, 08:20 </span>
-
Markus Klein commented and changed status
Under ReviewResolved done0 %100 % <span data-processor="relativetime" data-value="2026-10-22T08:25:13+00:00" > 10/22/26, 08:25 </span>Applied in changeset commit:3882002458d29e166f40f22d2aa7a6e245095714.
-
Tob Mit commented <span data-processor="relativetime" data-value="2026-10-26T07:17:14+00:00" > 10/26/26, 07:17 </span>
Markus Klein wrote in #note-6:
> @wat12luj Please test the change linked above, if this fits your needs.This fits my needs. Thank you very much for this fix.
I took the liberty to format your text a bit. Can you please confirm that this is really the exact log config you’re using?