- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
03-30-2026 05:26 AM
SSH Key verification and change is working, but reconciling is failing with error Permission denied or file is missing.
26.03.2026 03:50:12.517 | Info -> SSHConnectionHandler :: ExecuteSshCommand -> Running the command: copy file with preserve
26.03.2026 03:50:12.517 | Info -> SSHConnectionHandler :: SendCommand -> START
26.03.2026 03:50:12.517 | Info -> <>c__DisplayClass24_0 :: <SendCommand>b__0 -> Sending: cp -p /home/ruser/.ssh/authorized_keys /home/svccyarecon/authorized_keys_7569639101370124862791; echo $?\r
26.03.2026 03:50:12.533 | Info -> SSHConnectionHandler :: SendCommand -> END
26.03.2026 03:50:12.548 | Info -> <>c :: <Expect>b__21_0 -> Received: ccp -p /home/ruser/.ssh/a
u
uthorized_keys /home/svccyarecon/authorized_keys_7569639101370124862791; echo $
?
cp: cannot stat '/home/ruser/.ssh/authorized_keys': Permission denied
Please assist, what exact permission required on recon account svccyarecon for SSH Key rotation on Linux server? is there any other things to check?
03-30-2026 06:00 AM
Hi @Pradeep Kumar112
The error Permission denied indicates your reconcile account svccyarecon lacks the required permissions.
https://www.docs.cyberark.com/privilege-cloud-standard/Latest/en/Content/PASIMP/Plugin-SSH.htm
When UseSudoOnReconcile is set to No, the reconcile account must use a root user or a power user with root permissions. When UseSudoOnReconcile is set to Yes, the reconcile account must be in the sudoers list.
If the reconcile account user authenticates to the target server with a password, on the target machine, in sshd_config, set the PasswordAuthentication parameter to yes.
This is also confirmed in the SSH Key reconciliation documentation(https://docs.cyberark.com/pam-self-hosted/latest/en/content/sshkm/managing%20ssh%20keys.htm) and a CyberArk community thread where the user resolved the same issue by granting root privileges to the reconcile account. (https://community.cyberark.com/s/question/0D52J000070vSPgSAM/getting-permission-denied-error-while-reconciling-root-ssh-keys)
What to check:
Grant root-level privileges to svccyarecon on the target Linux server
Alternatively, set UseSudoOnReconcile = Yes in the platform parameters (in this case, the account must be in the sudoers list)
Verify permissions on the target machine:
authorized_keys file → 600
.ssh folder → 700
04-01-2026 03:00 AM
Thanks TeporeA,
I also noticed below statement from CyberArk doc.
"Reconcile account must use a root user or a power user with root permissions"
But Linux team having concern on root or power user with root permissions for reconcile account to rotate ssh keys because of highest privilege.
do we have any other approach where we can include only specific command for reconcile by default without assigning root level privileges?
or
can we update process.ini and prompt.ini file to include sudo prefix while running below command?
cp -p /home/ruser/.ssh/authorized_keys /home/svccyarecon/authorized_keys_7569639101370124862791; echo $?\r
04-01-2026 03:09 AM
Hi @Pradeep Kumar112
You can set it up as follows:
Set UseSudoOnReconcile= Yes in your platform
On the target Linux server (I'm not a Linux sysadmin, so you may want to double-check with your internal team):
Add this line in /etc/sudoers:
svccyarecon ALL = NOPASSWD: /usr/bin/cp
This allows the reconcile account to run only the cp command with sudo, without requiring a password.
If you need to allow additional commands:
svccyarecon ALL = NOPASSWD: /usr/bin/cp, /usr/bin/chmod, /usr/bin/chown
(These add chmod and chown if needed)
Let me know if this helps.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!

