My understanding is if the agent is running as root, it connects as ruu and effectively su's to id in the login object.
You can ssh with a key using the FTP agent using the issue remote commands option. This has to be enabled in the agent and is very limiting as you don't have and entire process block for running a full script. Its good for running a single command line.
on the flip side, you don't need an agent on the remote side.
Original Message:
Sent: May 22, 2025 12:29 PM
From: Daryl Brown
Subject: Running a jobs with a Login Unix machines via SSH Keys connection
I'm curious about this too...
Dunno if this might be helpful to you...
In our environment, our sysadmins have locked down certain accounts (service accounts) so that you cannot login to them directly -- you would have to login as your own user, and then 'su' over to the service account in question if you need to use one of those accounts yourself. That service account would have a password associated with it, but you wouldn't be able to login directly as that user. (I don't know exactly how the sysadmins restrict direct logins, but there's evidently some way to do it.) We put those service account credentials into our login object, and we're able to run jobs against that agent just fine.
So perhaps you could get around this problem if your sysadmins are allowed to create a password-authenticated user for Automic to use that does not allow direct logins?
Original Message:
Sent: May 22, 2025 11:50 AM
From: Sabine Arthur
Subject: Running a jobs with a Login Unix machines via SSH Keys connection
Hello
I'm trying to run an automic job on an automic agent .
The server is an ubuntu server that only accepts ssh key connections.
I've created a login object .
I leave the pwd empty .
But where should I store the ssh key?
Thank you for your help
------------------------------
Best regards,
Sabine
------------------------------