Dec 09, 2014
Karl Miles wrote
For the SSH encryption tunnel, there is currently only the option of authenticating with a password.
It would be preferable to be able to use a private key for the connection - particularly when accounts on the server have to be periodically changed in-line with security policy. In addition, we have to allow password authentication over SSH which we'd prefer to be able to remove.
The use of private keys is already present for the file transfer connection when SFTP is used, but it's not available for the database.
It would be preferable to be able to use a private key for the connection - particularly when accounts on the server have to be periodically changed in-line with security policy. In addition, we have to allow password authentication over SSH which we'd prefer to be able to remove.
The use of private keys is already present for the file transfer connection when SFTP is used, but it's not available for the database.
New
2 votes
Vote
Reply
1 Answer
Dec 10, 2014
Alex Pryshlivskiy
agent
wrote
Hello Karl,
Thanks for your suggestion and vote.
Your are right.
We have such option for FTP section. See screenshot - private-key.png
According to secure connection to database. This option in our future To-do list.
I guess we'll be able to implement such feature in 2015.
Right now we have 1 user request for this option.
Please vote to speed up implementation.
Thanks for your suggestion and vote.
Your are right.
We have such option for FTP section. See screenshot - private-key.png
According to secure connection to database. This option in our future To-do list.
I guess we'll be able to implement such feature in 2015.
Right now we have 1 user request for this option.
Please vote to speed up implementation.