search cancel

sftp key authentication issue

book

Article ID: 189407

calendar_today

Updated On:

Products

CA Workload Automation AE - Business Agents (AutoSys) CA Workload Automation AE - System Agent (AutoSys) CA Workload Automation AE - Scheduler (AutoSys) Workload Automation Agent CA Workload Automation AE

Issue/Introduction

The local HP-UX user account's home dir is on an NFS mount. 

Why would adding its private ssh rsa key in non-prod work, but not in prod? 

Manual SFTP client connections to same vendor work from either non-prod and prod, just not via the SFTP built-in agent.   

 

./cybAgent -v

CA Workload Automation Agent for:

   Linux x86_64 64-bit

   11.4, Service Pack 01, Maintenance Level 0, Build 1933


Enabled plug-in(s):

   - runner

   - router

   - filemon

   - objmon

   - filebrowser

   - ftp

   - database

Enabled Advanced Integration(s):

Built at: Jul 13 2018, 11:47:19

Environment

Release : 11.3.6

Component : CA Workload Automation AE (AutoSys)

Resolution

The reason from a command line sftp was allowing the client access but the autosys job would fail is the command line sftp will try multiple keys in your .ssh directory where the agent will not. It will only try the single one you specify in autosys_secure. The client did have a public key which the sftp command, from the command line, was eventually using to connect with. Once that was specified in autosys the sftp job ran without error.