Visit 3.4.2 requesting OTP for a server that does not use OTP

[visccyberacct]

I have a user that uses Visit on a regular basis. Recently the application has started requesting an OTP when the user attempts to open files on the remote server. The server has not asked for an OTP in the past and version 3.3 does not ask for the OTP.
The user connects to the remote server via ssh and kerberos before opening Visit and from my understanding Visit should be using the existing ssh connection

[cyrush]

@visccyberacct This could be a configuration or host name issue.

For example at LLNL: dane vs dane.llnl.gov will be treated differently by ssh with respect to key negotiation / connection.

VisIt will initiate a ssh connection (not using an existing connection, unless there is an external tunneling setup).

So they key is to get make sure passwordless to the desired host works.

I recommend outside of visit, they ssh to the exact host name visit is trying to connect to.

Depending on how they are launching, this may be displayed in a terminal when they run.

The remote name will be in the host profile, here is an example: (visit will try to ssh to dane.llnl.gov in this case)

Finally, they can run visit -debug 5 and look at the viewer logs for the hostname as well.