Access and Login

Connection Requirements

In order to provide a secure system, access to Kraken and Nautilus is available via the Secure Shell protocol (SSH). UNIX-based operating systems generally have an SSH client built in, available by typing "ssh user-name@resource.nics.tennessee.edu". Windows users may obtain free clients online, such as PuTTY.

Any SSH client used to log into NICS resources should:

• Support the SSH-2 protocol (supported by all modern SSH clients). Several security vulnerabilities exist in the SSH-1 protocol, therefore, access using a version 1 client is not allowed.
• Allow keyboard-interactive authentication to access NICS systems. For UNIX-based SSH clients, the following line should be in either the default ssh_configfile or your $HOME/.ssh/configfile:

   PreferredAuthentications keyboard-interactive,password

  The line may also contain other authentication methods, so long as keyboard-interactiveis included.

  For recent versions of SecureCRT or PuTTY, the change can be made through the SSH connection properties menu.

Connection Procedures

NICS supports secure access using gsissh (part of the Globus Toolkit) and secure access that requires the use of an RSA One Time Password (OTP) token which generates a one-time password. Secure access using the OTP is required to access HPSS storage and Nautilus.

One-Time Password Authentication

The OTP token is the authentication method that will be used to access NICS resources securely. To log in to NICS OTP systems, an OTP token is required.

You will receive your token in the mail after you follow the procedure outlined to verify your user information and activate your account . Once your OTP token has been enabled you will receive an email with instructions to set your four digit Personal Identification Number (PIN).
Setting up your One Time Password

Once you have set your PIN, you may log in using your OTP token. Use SSH to connect. In the example below, userid would be replaced by your NICS username. Users are prompted for their OTP token by the PASSCODE prompt. The PASSCODE is made up of your PIN, followed by the number displayed on the OTP token (see picture). For example, if your pin is 1234 and the token code is 987654, enter 1234987654.
Note: No characters will appear when entering your PASSCODE

% ssh your_userid@resource.nics.tennessee.edu
Enter PASSCODE:

Accounts that are not used for a period of three consecutive months are disabled. If you believe your account has been disabled for inactivity please submit a request to help@xsede.org or you may call the helpline directly at 865-241-1504. If you still cannot log in using your token once NICS re-enables your account please reply to help using the same ticket and request your token be re-enabled.

GSISSH Access

Kraken supports GSISSH using your XSEDE login password. Nautilus does not support GSISSH access. GSISSH is part of the Globus Toolkit, and the utility uses proxy certificates to authenticate. GSISSH allows single-sign-on capability to most XSEDE resources, where you have an account, without having to remember multiple usernames and passwords.

If GSI authentication fails, gsisshwill default to standard keyboard-interactive authentication (for OTP nodes, it prompts for your passcode). You can find steps for using GSISSH at Using Globus Tools.

userjd@ncsa:~> gsissh  gsissh.kraken.nics.xsede.org

File System Access

During times of system outage, access to a user's home and project directories is available at login.nics.tennessee.edu. The procedure for this is analogous to the Secure Access procedure. For example:

% ssh userid@login.nics.tennessee.edu
Enter PASSCODE:

Note that this system does not have access to the Lustre file system.

Connection Options

X11 Forwarding

There are some graphical tools you might want to use on NICS resources, which might require you to set up X11 forwarding, for example, there are a number of graphical debuggers and profilers as well as visualization tools. For instructions on setting this up, see Procedures for X11 forwarding.

Changing Your Default Shell

You may change your default shell, by logging into the NICS User portal.

RSA Key Fingerprints

Occasionally, you may receive an error message upon logging in to a system such as the following:

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!@
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that the OTP host key has just been changed.

This can be a result of normal system maintenance that changes an RSA public key or could be an actual security incident. If these fingerprints do not match what your SSH/secure copy (SCP)/secure file transfer (SFTP) client shows you, do not continue authentication; instead, contact help@xsede.org

HPSS Archival Storage Access

The HPSS archival storage system may be accessed using HSI. Use of HPSS archival storage resources requires OTP access. Password-free access is provided on the secure-access login nodes (ie if you used the OTP to log in).

File Transfer Utilities

The SSH-based SCP and SFTP utilities can be used to transfer files to and from NICS systems.

If GridFTP is available at your local site, this is the best way to transfer large files. For more information on data transfers, see the data transfer page in the general support section.

The URLs for NICS GridFTP servers are: