Start a new topic

Store username in connection instead of credential for SSH

In our organization, as a new administrator completes the onboard process, they are told to generate an SSH key pair. This SSH key pair is used throughout their entire employment.


Once the new administrator has generated an SSH key pair, the public key is copied to the authorized_keys file across various servers under various usernames.


In Royal TS, the username is tied to the credential, but because the username cannot be overridden in the connection, specifying different usernames while using the same key is impossible without creating duplicate credentials.


For example:

User A sets up Credential A

User A sets up Connection A

Connection A needs to connect to Server A as root

User A sets up Connection B

Connection B needs to connect to Server A as dba

User A sets up Connection C

Connection C needs to connect to Server B as root


Can the ability to override the username stored in a credential with a username stored in a connection be added to a future version of Royal TS?

1 person likes this idea
1 Comment

Hi Leonardo,

the current architecture doesn't allow this kind of "override" in the near future but we are working on something which may helpful in this scenario.


1 person likes this
Login or Signup to post a comment