In general, most modern SSH clients will work with 2FA without any extra configuration.
If you run into problems, ensure that your client tries the “keyboard-interactive” authentication method (i.e not “password”).
Example:
ssh -o PreferredAuthentications=keyboard-interactive x_examp@duolith
Unless your SSH client hides or translates the prompts, you should first be asked for your NSC cluster password (“Password:”) and then the 6-digit TOTP code (“Verification code:”). Example:
$ ssh x_examp@duolith
Password:
Verification code:
Last login: Mon May 3 13:10:24 2021 from ventus.lan
[x_examp@duolith ~]$
Below you can find detailed configuration and screenshots for some SSH and file transfer clients we have tested.
Note: this does not mean that other clients won’t work!
Recommended Linux clients and how to configure them
Recommended macOS clients and how to configure them
Recommended Windows clients and how to configure them
Recommended IOS clients and how to configure them
How to use the Thinlinc client
Guides, documentation and FAQ.
Applying for projects and login accounts.