The private key authentication fails when importing the key in the connection file
When configuring a connection to use private key authentication, the client allows for the import of the key in the connection file. This file can be shared across multiple clients without the need to move the private key around. An issue currently prevents the correct key being imported, thus causing the generated connection file to fail to correctly authenticate to the server.
In order to work around the issue, the connection file importing the private key can be created on a NoMachine desktop client and copied to the mobile device.
SOLVED, Released in version 8.4.2
