Unable to authenticate to SFTP using SSH Keys
View some of the Frequently Asked Questions to our support staff. Included are some tips and tricks making this forum ideal for users getting started with GoAnywhere Services. Note: Users can reply to existing topics but only our support staff can add new topics to this forum.
5 posts
Page 1 of 1
- Support Specialist
- Posts: 11
- Joined: Fri May 08, 2009 8:59 am
When configuring a web user's authentication settings to SFTP you can allow the user to authenticate using a public SSH key. This can replace the need for a password or enhance your security settings by forcing the user to provide both a password and a key.
In order for this to work you must place the web users public key into the *installation folder*/userdata/keys/ssh/ directory. The file name must match the user name with the .pub extension (e.g. jsmith.pub).
Update
With version 3.1.0 and later of GoAnywhere Services, this process has changed. The SSH keys are now stored in the GoAnywhere Services database and are no longer stored on the file system. Please refer to the Web Users SSH Keys section of the GoAnywhere Services User's Guide for more information.
In order for this to work you must place the web users public key into the *installation folder*/userdata/keys/ssh/ directory. The file name must match the user name with the .pub extension (e.g. jsmith.pub).
Update
With version 3.1.0 and later of GoAnywhere Services, this process has changed. The SSH keys are now stored in the GoAnywhere Services database and are no longer stored on the file system. Please refer to the Web Users SSH Keys section of the GoAnywhere Services User's Guide for more information.
- Support Specialist
- Posts: 11
- Joined: Fri May 08, 2009 8:59 am
I'm glad this topic was able to assist you. I will make sure the help documentation is updated with SFTP key authentication information in the next release.
Support_Steve wrote:When configuring a web user's authentication settings to SFTP you can allow the user to authenticate using a public SSH key. This can replace the need for a password or enhance your security settings by forcing the user to provide both a password and a key.
In order for this to work you must place the web users public key into the *installation folder*/userdata/keys/ssh/ directory. The file name must match the user name with the .pub extension (e.g. jsmith.pub).
Does importing a public key via "SSH Key Manager" and then associating that key with the WebUser accomplish the same results? Or do I still need to go place the .pub file into the /userdata/keys/ssh directory?
- Support Specialist
- Posts: 62
- Joined: Thu Jul 19, 2012 9:15 am
- Location: Ashland, NE
-
You are correct. This post was from a few years back and we have changed how we manage SSH keys in GoAnywhere Services. With the 3.1.0 release, we started storing SSH keys in the GoAnywhere Services database and no longer stored them on the file system.
I will update the original post to indicate that those details are for pre 3.1.0 installations and then add specifics on how it changed moving forward.
We do have a section specific to this topic within the GoAnywhere Services User's Guide titled Web User SSH Keys that outlines that process.
Thanks - Jon
I will update the original post to indicate that those details are for pre 3.1.0 installations and then add specifics on how it changed moving forward.
We do have a section specific to this topic within the GoAnywhere Services User's Guide titled Web User SSH Keys that outlines that process.
Thanks - Jon
5 posts
Page 1 of 1