When attempting to use host.update for changing tls_psk attributes - either key or identity - for parent host and related hosts created from host prototypes under it (which share/inherit the TLS PSK configuration) an error is returned.

The host.massupdate method allows this, but is removed in the upcoming release, leaving a lack for the functionality above.

It should be also prohibited to include the discovered hosts with either method - the change should happen on the parent (containing the discovery) host only and be propagated to related discovered hosts by server.

Steps to reproduce, scenario 1

• Create a host with discovery of host prototypes.
• Execute discovery.
• Run host.massupdate on the parent host and related discovered hosts, changing TLS PSK details.

Result
Update succeeds.

Expected
Error telling it is prohibited to update read-only attribute for the discovered hosts.

Steps to reproduce, scenario 2

• Run host.update changing either the TLS key or identity on the parent host only.

Result:
Error "Invalid parameter "/1/tls_psk": another tls_psk value is already associated with given tls_psk_identity."

Expected
Success. Both parent host and related discovered hosts' TLS PSK details match after (re)discovery.

The error should be shown only if updating to a key+identity pair in use by another entity (host, proxy, ...).