Idea ID 1656113
Permit reversion to the RSH/REXEC push installation mechanism for Linux clients
Benefits / Value:
In some customer environments it may not be possible or desirable for the team that manages & supports Data Protector to be provided with credentials for Linux clients for the purpose of push installation from an Installation Server via SSH as these credentials would permit access outside of the DP environment. The same reasoning may also not permit establishing SSH trust between Data Protector Linux clients and any Installation Servers.
Permitting reversion to the RSH/REXEC mechanism used pre-DP10 would allow a customer in this situation to preserve their existing access model for Linux clients albeit with the acceptance that Linux push installation traffic would remain unencrypted.
Implemented as a Global variable. Setting the variable could either result in failback to RSH/REXEC if no credentials / no SSH trust was provided for a client / set of clients, or bypass SSH push installation completely in favour of RSH/REXEC.
Secure installation via non-Data Protector methods e.g. rpm installation via Red Hat Satellite for RHEL clients, would be a suitable alternative were it not for the fact that there is no supported patch deployment mechanism other than via the DP IS.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.