#109213Discrepancy between generated password display and actual input value when using passwordGenerator with allowEdit
Description
Status Quo
In TYPO3, the TCA type password can be extended with a fieldControl of renderType passwordGenerator. When the option allowEdit is set to true, users are expected to be able to modify the password after it has been generated by the tool.
Observed Behavior
When a user clicks the button to generate a password, the password is displayed in plain text within the generator’s interface. If the user then utilizes the allowEdit functionality to manually adjust specific characters in that plain text string (for example, replacing complex special characters with simpler ones), these manual changes are not synchronized back to the underlying hidden HTML input field.
As a result, when the record is saved, the originally generated password is persisted in the database instead of the modified version the user actually sees on their screen. This leads to a situation where the user attempts to log in with their modified password and fails, as they are unaware that their edits were never processed by the FormEngine.
Expected Behavior
The fieldControl should ensure two way synchronization. If allowEdit is enabled and a user modifies the generated string, the value of the actual password input field must be updated accordingly before the record is saved.
Alternatively, a native reveal mechanism (similar to the eye icon common in modern web interfaces) should be considered for the password field type. This would allow users to verify their input during the typing process without relying on the passwordGenerator’s display, which currently seems to act as a detached overlay once the generation happens.
Impact
This behavior causes confusion and lockout scenarios for backend users, as the password stored in the system does not match the password the administrator intentionally typed or modified during the user creation or editing process.
Reviews 1
Related issues 1
History 6
-
Garvin Hicking commented and changed status
NewNeeds Feedback <span data-processor="relativetime" data-value="2026-03-12T11:27:33+00:00" > 03/12/26, 11:27 </span> -
Garvin Hicking changed Related to #69190 <span data-processor="relativetime" data-value="2026-03-12T11:27:40+00:00" > 03/12/26, 11:27 </span>
-
Simon Schaufelberger commented <span data-processor="relativetime" data-value="2026-03-12T11:31:58+00:00" > 03/12/26, 11:31 </span>
No, the
'renderType' => 'passwordGenerator',has not been deprecated, only the options. My change uses the existing renderType as well, so I did not introduce this bug. -
Stefan Froemken commented <span data-processor="relativetime" data-value="2026-03-12T14:00:29+00:00" > 03/12/26, 14:00 </span>
How should this issue apply to me? I have this issue in TYPO3 13.4. Your link is from a TYPO3 14.2
-
Garvin Hicking commented <span data-processor="relativetime" data-value="2026-03-12T15:12:50+00:00" > 03/12/26, 15:12 </span>
Stefan Froemken wrote in #note-4:
> How should this issue apply to me? I have this issue in TYPO3 13.4. Your link is from a TYPO3 14.2Because if this was changed in v14 it would become less likely that a backport bugfix might be made for scenarios that no longer apply.
I’m retreating from this issue but I hope you can find a solution.
-
Stefan Froemken commented and changed status
Needs FeedbackClosed <span data-processor="relativetime" data-value="2026-10-02T12:54:46+00:00" > 10/02/26, 12:54 </span>Hello,
I cannot reproduce this issue anymore in TYPO3 13.
After pressing password generation button:
=== VISIBLE FIELD === Value (.value): @k~<(3PTvDaX === THE RELATED HIDDEN FIELD === Value (.value): @k~<(3PTvDaX
Perfect. Both input fields have same new value.
Now, I modify the password and replace all special chars with ! and clicked somewhere (focus-out):
=== VISIBLE FIELD === Value (.value): ******** === THE RELATED HIDDEN FIELD === Value (.value): !k!!!3PTvDaX
That’s the way it has to be. Perfect.
IMO something has changed in Core in the meanwhile. Thank you. Closing this issue.
Stefan
With #69190 this passwordGenerator has been deprecated and is superseded:
https://review.typo3.org/c/Packages/TYPO3.CMS/+/92647/29/typo3/sysext/core/Documentation/Changelog/14.2/Deprecation-69190-DeprecatePasswordRulesOptionInPasswordGeneratorFieldControl.rst
Does the issue apply to you with that new variant?