Description of problem:

Once you set the remote_execution_ssh_password setting, you can not change it back to None. Also it is not possible to override it to None when running remote execution.

How reproducible:

Always

Is this issue a regression from an earlier version:

TBA

Steps to Reproduce:

1. [pre-step]on a fresh Satellite, observe the list of settings in database

foreman=# select * from settings;

2. In Satellite UI, under settings > remote execution, set the Default SSH password setting to something. The entry appears in the settings table:

  7 | remote_execution_ssh_password            | encrypted-MWoyd0tOS3FkVkFzSERLMjdmK1QzY2g5TCsxSjhady9QUXc1aHlxWjJybz0tLXBEbGN0SjdaV25Scmh6VC9rNk93WVE9PQ==--8589a93537ad253
14a4c1b9e1f2003eafba29a18 | 2025-01-13 12:20:54.262421 | 2025-01-14 12:24:54.078431

3. Back in the UI change the setting back to an empty value. Check the settings table again:

  **  7 | remote_execution_ssh_password            | encrypted-V3RKbC9MVC9rSTVNVTdwMVh5RE9MSFpBQkpuakJoZkVvK3VzNEQ0dVpqWT0tLUYzb2pBcVFkSWtMOU41enFjS2pHSmc9PQ==--7c61b5673ff8a27
b94e3ce2807dbd2aeaec190fa | 2025-01-13 12:20:54.262421 | 2025-01-14 12:26:18.797732

Actual behavior:
The setting remains set, it is updated to a different encrypted value (not sure what value is that exactly)

Expected behavior:
After clearing the value in UI, the db item should be cleared or set to an empty value – it works like this for example with the Effective user password setting

Business Impact / Additional info:

The remote_execution_ssh_key_passphrase seems to be affected by this as well.

Might be separate issue, but when running remote execution via cli and trying to override the password setting using --password="", the override doesn't seem to take place and the default setting is used.