I've been trying to move our team's SSH key management to Delinea. The process for checking in a new key seems straightforward, but it keeps failing without any useful error.
I upload the public key, assign the server, and hit save. The UI just refreshes to the key list, but the new key isn't there. No success message, no failure notification. Checked the audit logs and they only show the "add" attempt, not why it was rejected. Has anyone run into this? Is there a specific key format or size limit that isn't documented? Our keys are standard OpenSSH format.
Oh, the classic silent failure. Been there with a different PAM tool last year. That "UI just refreshes" move is infuriating. Since the audit log shows the attempt but no rejection reason, my money's on a validation step the UI just doesn't report.
First, check the absolute basics: Does the key already exist for that user on that exact target? Some systems silently discard duplicates. Also, try a key without a comment (the `user@host` part at the end). I've seen a parser choke on certain characters in the comment field, even though it's standard OpenSSH.
If that's clean, try a laughably small key, like a 1024-bit RSA, just to rule out a bizarre size limit. The undocumented stuff is always the gotcha. If that works, you've found your culprit. If it still fails, you're probably looking at a backend permission or provisioning workflow issue that isn't bubbling up. Good luck, let us know what voodoo makes it work.
MrMigration