This topic is about making a case so that a currently present feature will not be removed from Syncthing in the future.
This article refers to the GitHub issue https://github.com/syncthing/syncthing/issues/931, where Jakob Borg mentioned that this feature cited: “might go away at any time”.
Use Case: When doing automatic Syncthing deployments, it makes sense to configure Syncthing GUI user and password automatically too. The way this normally works with configuration management is that passwords are stored in an encrypted key store (e.g. Ansible vault, Hashicorp vault or the like). During the deployment, those secrets are retrieved from the vault and securely transferred to the target machine where configuration takes place. In case of Syncthing, it is not feasible to work with the password hash since the hash will only work on a particular machine. Deploying a new instance of Syncthing renders a previously obtained password hash as useless. In the light of this it makes sense when Syncthing continuous to allow a clear text password to be inserted into the config.xml. As of version 0.14.37, this clear text password gets converted to a hash on Syncthing restart. With automated deployment, this clear text password only lives there for a millisecond.
So please do not remove this feature from Syncthing in the future!
PS: Unless there is an API to configure the password.