I've tried to configure an Agentless Remote Connection,
See this picture:
When I hit the test button I got this error message: Connection test failed (detail information: authentication error)
But when I test from any other Linux System to login with the same credentials, it works ! ;-)
When the Connection Test was run, I see the following error message on the Target Linux System:
Jan 11 15:02:58 starhawk sshd: Accepted password for haduser from 192.168.71.198 port 54139 ssh2
Jan 11 15:02:59 starhawk sshd: pam_unix(sshd:session): session opened for user haduser by (uid=0)
Jan 11 15:03:00 starhawk unix_chkpwd: password check failed for user (root)
Jan 11 15:03:00 starhawk su: pam_unix(su-l:auth): authentication failure; logname=haduser uid=501 euid=0 tty=pts/2 ruser=haduser rhost= user=root
Jan 11 15:03:03 starhawk sshd: Received disconnect from 192.168.71.198: 11: The user disconnected the application
Jan 11 15:03:03 starhawk sshd: pam_unix(sshd:session): session closed for user haduser
What I can see here, the basic login as user haduser was successful, then the "Agentless Remote Connection" is playing something with the root user. And I see that the command "su -l" was executed and this failed. Of course - and I don't want that something should be made by the user root.
Question: Why the "Agentless Remote Connection" needs to switch into root user account ?