We have Rundeck connecting to many different application servers to help application teams to do their deployment. Two teams reported the below authentication failure error, one for a linux node, the other for a windows node.
Error:
Authentication failure connecting to node: "<node>". Make sure your resource definitions and credentials are up to date.
For the linux node issue, it's because user was using passwordless ssh to connect to their linux box, but the public key wasn't setup properly. The connection didn't even work from Rundeck server to their box. The problem was resolved after having user changed the permission of their public key file.
For the windows node issue, it's because user was using a "script" (inline script) job step, instead of the simple "command" job step. It looks like this "script" job step is for unix only, and because user was using it, the netstat from user's windows box showed that Rundeck was trying to connect to the port 22 (default ssh port) in their windows box. Replacing the inline script with a simple command step fixed the issue.
