Granite

Granite publishes no SSH public-key setup procedure, and there is no login node to install a key on. If you have set up an SSH keypair for another ACCESS resource, it does not apply here. The only SSH-reachable Granite host is the read-only quota reporter described below, and it authenticates with your NCSA password plus a Duo prompt. Access Methods.

Step 1 - Get an NCSA (Kerberos) identity

Granite authenticates against your NCSA identity, which is separate from your ACCESS identity. Create or manage it at the NCSA Account Portal. NCSA Account Portal | Create a Kerberos account | Granite allocations guide. 

Step 2 - Enroll in NCSA Duo (two-factor authentication)

You must enroll with Duo before your first login attempt. Before you start, have your NCSA Kerberos username and account, and install the Duo Mobile app. Then enroll through the NCSA Duo portal. Duo at NCSA - enrollment guide.

Step 3 - Generate and store backup codes

Immediately after enrolling, generate two backup codes and store them somewhere other than the phone running Duo - these 8-digit codes are how you authenticate if the device is lost or replaced. In the Duo portal, choose Manage Backup Codes and Tokens, then Generate replacement backup codes.

Step 4 - Check your quota

You will be prompted for your NCSA password, then for Duo - either push ("Duo Push to XXX-XXX-1234") or a typed passcode. On success the host prints a table of your Taiga and Granite usage - block used, soft quota, hard limit, files used, inode soft/hard - and then immediately disconnects. This is a read-only reporter: it does not give you a shell, and there is nothing to run once connected. Usage and Quota Controls — full worked example.

Getting an allocation

Granite offers three allocation paths - NSF ACCESS, Illinois Computes, and direct investment. Granite allocations guide.