This article provides details on some of the common issues users may see while using MobaXterm with ASA. 

Common Issues:

1. sft command fails with the following error. Usually, this is seen when the sft client is installed for all users (advanced setting during installation or through sccm).

   bash: syntax error near unexpected token `('

2. An error like the one below can also be seen after successfully connecting to the target server:

   Pseudo-terminal will not be allocated because stdin is not a terminal.

3. While using the client in MobaXterm this error is seen.
   error: error interacting with system keyring: data was encrypted with a different keyring configuration and cannot be decrypted

• Okta Advanced Server Access (ASA)
• MobaXterm
• Secure Shell (ssh)

Matches Common Issues in Overview

1. Launching sft.exe.
   1. There is an issue with the sft.exe being launched because the PATH is not specified or the PATH can not be referenced. This can happen if there are spaces in the folder name like "Program Files (x86)" .
2. Pseudo-terminal error.
   
   1.  It is recommended to use proxycommand with MobaXterm to avoid this error. 
3. Using the client throws a Keyring error.

1. To fix the PATH issue.

The PATH variable refers to every folder that will be examined when running an executable. In MobaXterm, "Use Windows PATH" should be selected, as depicted in the screenshot.

Once that is set, relaunch the application and test executing sft again. If it still not working then the PATH can be examined further by displaying the variables' contents in MobaXterm with the command below:

• echo $PATH

Compare the output by executing the following in the Windows cmd prompt:

• echo %PATH%

If the path is correct, then try calling sft.exe using the full path. 

• 'c://Program Files (x86)/ScaleFT/bin/sft.exe'

Here is an example of a successful output:

There are times when the "Program Files (x86)" folder can cause an issue because of the spaces in the name. Windows short names can be used for the folder name with spaces in those cases. Generally, PROGRA~2 will be the one for "Program Files (x86)" that can be added to the path variable. This should be done on the Windows side as this is where MobaXterm pulls the configuration from (relaunch MobaXterm if Windows variables are updated).

• c://PROGRA~2/ScaleFT/bin/sft.exe

If the path is not working properly, an alias can always be used. This is a command that can reference another command:

• To add the alias: 

  • alias sft=c://PROGRA~2/ScaleFT/bin/sft.exe

• To view the alias: 

  • alias sft

• To remove the alias:

  • unalias sft

2. To fix the Pseudo-terminal error.

Use instructions to set up the proxy command. The proxy command allows the ssh (or scp) utility to be used with ASA without needing to specify sft(sft ssh <server hostname>). However, the user must be logged in (sft login) to sft to use proxycommands. Once set, users will be able to connect to a server using the following command:

• • ssh <server hostname | ip address>

The following steps can be used to save a session by connecting to the target server at startup. 

• Click Session > click Shell > click Advanced Shell Settings.
• In the "Execute the following commands at startup:" add the sft commands and click OK. This will save the session. Please see the screenshot of the example below:

NOTE: Okta ASA only supports SSH (not RDP) for MobaXterm.

3. To fix the keyring issue.

The client needs to be unenrolled and re-enrolled. This cannot be done from the MobaXterm application and must be performed using PowerShell or the Command Prompt in Windows. From one of those applications, run the following: 

sft unenroll

And to re-enroll, run this command:

sft enroll

Related References

• sft client commands
• MobaXterm Setup