#107089Warn on resetting install tool password via console command when overridden
Description
when the install tool password is overridden in the config/system/additional.php
it cannot be changed with the newly introduced command `typo3 install:password:set`.
We should warn about the fact so as not to confuse new Integrators / Administrators.
Reviews 1
Related issues 3
History 924
-
Garvin Hicking commented and changed status
NewNeeds Feedback <span data-processor="relativetime" data-value="2025-07-14T08:31:08+00:00" > 07/14/25, 08:31 </span> -
Benjamin Franzke commented and changed status
Needs FeedbackAccepted <span data-processor="relativetime" data-value="2025-07-14T09:05:48+00:00" > 07/14/25, 09:05 </span>Garvin Hicking wrote in #note-1:
> Do you have a proposal how to achieve this? Sounds a bit complicated because it would require a follow-uo request and a new bootstrap with backend context tk see if the password takes effect.Load a non-overwritten configuration via
ConfigurationManager->getMergedLocalConfiguration()(does not load additional.php) and compare that to the current value as in https://github.com/TYPO3/typo3/blob/4929400759e583fad5ad6556a600e5ea5c240cba/typo3/sysext/install/Classes/Service/LocalConfigurationValueService.php#L113This could be done preemptive, before attempting to change the value.
I would not do a post-save check, as it’s complicated as you mentioned.
A warning that is printed before asking for the new password should be sufficient. -
Garvin Hicking changed Related to #104058 <span data-processor="relativetime" data-value="2025-07-14T14:16:18+00:00" > 07/14/25, 14:16 </span>
-
Garvin Hicking changed Related to #107088 <span data-processor="relativetime" data-value="2025-07-14T14:16:25+00:00" > 07/14/25, 14:16 </span>
-
Garvin Hicking commented <span data-processor="relativetime" data-value="2025-07-14T14:22:30+00:00" > 07/14/25, 14:22 </span>
Note to self: This comparison might not catch setups where a settings.php and additional.php both contain the same installToolPassword hash. In this case the strings would be identical, but changing it in settings.php would not take effect.
Not sure how to detect such a setup, so I would say: Add a disclaimer about this, and do the “value is different” check as suggested, because it improves situations where we CAN detect differences.
-
Garvin Hicking changed Related to #107087 <span data-processor="relativetime" data-value="2025-07-14T14:30:00+00:00" > 07/14/25, 14:30 </span>
-
Garvin Hicking changed assigned to Garvin Hicking <span data-processor="relativetime" data-value="2025-07-14T14:32:13+00:00" > 07/14/25, 14:32 </span>
-
Gerrit Code Review pushed patch set 8 for main to change 90099 status
AcceptedUnder Review <span data-processor="relativetime" data-value="2025-07-21T09:36:11+00:00" > 07/21/25, 09:36 </span> -
Gerrit Code Review pushed patch set 9 for main to change 90099 <span data-processor="relativetime" data-value="2025-07-21T09:39:06+00:00" > 07/21/25, 09:39 </span>
-
Gerrit Code Review pushed patch set 10 for main to change 90099 <span data-processor="relativetime" data-value="2025-07-21T11:26:58+00:00" > 07/21/25, 11:26 </span>
-
Gerrit Code Review pushed patch set 11 for main to change 90099 <span data-processor="relativetime" data-value="2025-07-21T11:27:42+00:00" > 07/21/25, 11:27 </span>
-
Gerrit Code Review pushed patch set 12 for main to change 90099 <span data-processor="relativetime" data-value="2025-07-21T11:29:27+00:00" > 07/21/25, 11:29 </span>
-
Gerrit Code Review pushed patch set 13 for main to change 90099 <span data-processor="relativetime" data-value="2025-07-21T12:46:19+00:00" > 07/21/25, 12:46 </span>
-
Gerrit Code Review pushed patch set 14 for main to change 90099 <span data-processor="relativetime" data-value="2025-07-21T14:32:18+00:00" > 07/21/25, 14:32 </span>
-
Gerrit Code Review pushed patch set 15 for main to change 90099 <span data-processor="relativetime" data-value="2025-07-26T19:28:55+00:00" > 07/26/25, 19:28 </span>
-
Gerrit Code Review pushed patch set 16 for main to change 90099 <span data-processor="relativetime" data-value="2025-08-08T09:55:51+00:00" > 08/08/25, 09:55 </span>
-
Gerrit Code Review pushed patch set 17 for main to change 90099 <span data-processor="relativetime" data-value="2025-08-08T10:38:53+00:00" > 08/08/25, 10:38 </span>
-
Gerrit Code Review pushed patch set 19 for main to change 90099 <span data-processor="relativetime" data-value="2025-09-10T14:18:46+00:00" > 09/10/25, 14:18 </span>
-
Gerrit Code Review pushed patch set 20 for main to change 90099 <span data-processor="relativetime" data-value="2025-09-12T07:51:54+00:00" > 09/12/25, 07:51 </span>
-
Gerrit Code Review pushed patch set 21 for main to change 90099 <span data-processor="relativetime" data-value="2025-12-12T10:31:16+00:00" > 12/12/25, 10:31 </span>
-
Gerrit Code Review pushed patch set 22 for main to change 90099 <span data-processor="relativetime" data-value="2025-12-12T18:55:14+00:00" > 12/12/25, 18:55 </span>
-
Gerrit Code Review pushed patch set 23 for main to change 90099 <span data-processor="relativetime" data-value="2026-01-10T17:56:53+00:00" > 01/10/26, 17:56 </span>
-
Garvin Hicking commented and changed status
Under ReviewResolved done0 %100 % <span data-processor="relativetime" data-value="2026-01-14T10:20:10+00:00" > 01/14/26, 10:20 </span>Applied in changeset commit:8cc147f7b0ae3189427ab6a9a17bcd176c1aeea4.
-
Benni Mack changed status
ResolvedClosed <span data-processor="relativetime" data-value="2026-03-31T09:00:43+00:00" > 03/31/26, 09:00 </span>
Do you have a proposal how to achieve this? Sounds a bit complicated because it would require a follow-uo request and a new bootstrap with backend context tk see if the password takes effect.
IMO if an admin overrides this setting they should be aware of theor individual aettings overrriding this.
We could add a disclaimer in the help output of the command?