Devolutions ForumDevolutions Forum

SCP entries not honoring the username format

SCP entries not honoring the username format

avatar
Isaac

I have two entries which reference the same user credentials, both with the Username format (under Advanced) set to {Domain}\{User}. The SSH entry uses this custom format, both with using the 'view password' function, and when connecting as SSH logs a connection using 'username@domain'. The SCP entry does not appear to use the username format: in view password I only see the username without the domain, and the server logs an attempted SSH connection using only 'username'. Is this a bug or is there some other configuration I should change so that SCP will connect with 'username@domain'?

Thanks!

All Comments (6)

avatar
James Lafleur

Hello,

Thank you for contacting us on that matter!

Would it be possible for you to provide us with your version of RDM and the type of data source that you are currently using?

The username format of an SCP entry can also be changed under the "Advanced" section of your SCP entry and should be honored when you use the "View Password".

Best regards,

James Lafleur

avatar
Isaac

I am using 2023.1.20.0 64-bit.

The data source is an ubuntu server, and the ssh connection to that server does work. I have the username format on both items (ssh and scp) configured the same, but the username format in View Password is different.

avatar
Isaac

PS: here is the connection as copied from Devolutions, replacing a few field values of course.

<?xml version="1.0"?>
<ArrayOfConnection>
  <Connection>
    <ConnectionType>Scp</ConnectionType>
    <CreatedBy>domain\user</CreatedBy>
    <CreationDateTime>2023-06-01T19:04:29</CreationDateTime>
    <CredentialConnectionID>88E4BE76-4C5B-4694-AA9C-D53B7E0FE0DC</CredentialConnectionID>
    <CredentialPrivateVaultSearchString>credentialname</CredentialPrivateVaultSearchString>
    <ID>7845621b-74bd-48b7-bd73-7269268d1b9d</ID>
    <Name>scp</Name>
    <OpenEmbedded>true</OpenEmbedded>
    <UpdateDateTime>2023-06-26T16:53:23</UpdateDateTime>
    <UpdatedBy>domain\user</UpdatedBy>
    <UserNameFormat>UserAtDomain</UserNameFormat>
    <Scp>
      <Host>ip address</Host>
    </Scp>
  </Connection>
</ArrayOfConnection>


And here is the credential, again replacing fields: 

<?xml version="1.0"?>
<ArrayOfConnection>
  <Connection>
    <ConnectionType>Credential</ConnectionType>
    <CreatedBy>domain\user</CreatedBy>
    <CreationDateTime>2023-04-11T11:18:33</CreationDateTime>
    <ID>8de12980-bdb7-47e9-bfb5-9edeaebaacc5</ID>
    <Name>credentialname</Name>
    <UpdateDateTime>2023-06-26T17:13:07</UpdateDateTime>
    <UpdatedBy>domain\user</UpdatedBy>
    <Credentials>
      <Domain>domain</Domain>
      <SafePassword>pass</SafePassword>
      <UserName>user</UserName>
    </Credentials>
    <MetaInformation>
      <AssociatedEmail>prefix@domain.com</AssociatedEmail>
    </MetaInformation>
  </Connection>
</ArrayOfConnection>
avatar
Samuel Dery

Hello Isaac,

Thank you for your reply,

I see, I'm wondering if there is a specific reason why you're using an SCP entry type in this case?

Perhaps using your SSH Shell entry with the "Use SFTP for remote file transfer" option enabled under the "Terminal" -> "Advanced" section may work better for you?

Let me know,

Best regards,

Samuel Dery

avatar
Isaac

Because I didn't know it was an option, thank you for pointing it out!

It would be nice to get the scp entry fixed, not sure there is a way I can log that as a defect, but so far it looks like this is a viable workaround for me.

avatar
Samuel Dery

Hello Issac,

Thank you for your reply,

We usually recommend using SFTP over other options if it is working, so I'm glad to hear that it's working for you in this case!

If you start encountering any issues with this new method feel free to let me know,

Best regards,

Samuel Dery