Issue Bug Closed

#106743Creating new BE users now requires additional authentication

Sybille Peters 05/21/25, 12:30 updated 12/02/25, 13:59

Description

The change introduced with Require step-up authentication for password change and https://forge.typo3.org/issues/103252 requires authentication when changing password.

IMHO, this is unnecessary when creating new users and can be quite a nuisance for setting up new users.

Side note:

(Additionally, for most users we don’t even need the password because we use external login server (SSO). We also have introduced a field where you can select the login type. It would probably make sense to remove the password field, if native login is not supported, however I would prefer if a mechanism for this was introduced in core, since extensions implementing this would probably result in conflicts if you want to provide several.)

login_methods.png

Versions

  • change was applied to >= v12
  • noticed change in v12

Reviews 12

Files 1

History 919

  1. Oliver Hader commented <span data-processor="relativetime" data-value="2025-05-22T12:04:50+00:00" > 05/22/25, 12:04 </span>

    https://review.typo3.org/c/Packages/TYPO3.CMS/+/89491 would introduce a new event that allows to by-pass the step-up authentication. Would that be a feasible alternative for your use-case?

  2. Sybille Peters commented <span data-processor="relativetime" data-value="2025-05-22T15:46:02+00:00" > 05/22/25, 15:46 </span>

    Oliver:
    > Would that be a feasible alternative for your use-case?

    Yes, theoretically yes (did not test the patch yet). Thank you for responding.

  3. Oliver Hader commented <span data-processor="relativetime" data-value="2025-05-26T09:44:33+00:00" > 05/26/25, 09:44 </span>

    I wanted to leave feedback on the assumption in the original issue description:

    Sybille Peters wrote:
    > IMHO, this is unnecessary when creating new users and can be quite a nuisance for setting up new users.

    The basic concepts of the underlying problem are referenced in https://cwe.mitre.org/data/definitions/620.html

    Allowing to create new users without verification would allow an attacker to create a new admin user which can be used further.
    This also applies when creating new non-admin users, since the it would allow to grant privileges generously.

  4. Oliver Hader commented and changed status Under Review Resolved done 0 % 100 % <span data-processor="relativetime" data-value="2025-05-27T13:25:07+00:00" > 05/27/25, 13:25 </span>

    Applied in changeset commit:76d48d96e646111ea6681abcc19225410edca96b.

  5. Sybille Peters commented <span data-processor="relativetime" data-value="2025-06-02T07:39:24+00:00" > 06/02/25, 07:39 </span>

    Feedback after patch: I debugged the new version and it looks like in DataHandlerAuthenticationContext::processDatamap_postProcessFieldArray that it would be able to detect that a new BE user is being created (dataHandler->datamap->be_users[NEW….) if BE user is created via normal process. In this case, I don’t really see why it should be necessary to query the sudo login if a new user is being created and a new password assigned.

    I understand we can now use the events but it makes adding code necessary.

    (sorry, I should have commented this before, but I am currently still a bit disabled after an accident).