To login to a Resource Provider (RP), you will often need to upload or copy your public SSH key to the RP. (Note: a few RPs support ssh via username and passwords in which case, uploading an ssh key is not required). RPs support different methods for uploading your public SSH key, as indicated in the following table:

In the next section, we present a high-level overview of the five basic approaches RPs support for uploading public SSH keys (a sixth approach based on the SSO Hub will only work until Aug 31, 2022). We then describe the specific upload process – which must be done once (prior to SSH’ing to the RP). Ultimately, your public SSH key needs to be added to a file of authorized keys (usually the file named ~/.ssh/authorized_keys) on the RP machine. (Note: Complete information about logging into each RP – including instructions to upload your public SSH key – can be found in the Logging in to Resource Providers page).

Upload Approaches

1. Upload via an RP's Open-On-Demand Server: If the RP operates an Open-On-Demand service, users can login to the RP’s Open-On-Demand web server with their ACCESS user ID and password. Using the Open-On-Demand web interface, they can launch a terminal window (in their browser) that is logged into one of the RPs login nodes. They can then cut/paste their public key into the terminal window to place their public key in the .ssh/authorized_keys file on the RP’s login node.

2. Upload via the ACCESS ID Management system (Coming Soon): Users can login to the ACCESS ID Management web service using their ACCESS user ID and password. The ACCESS ID Management Web Service allows users to upload their public key which will be saved by ACCESS (in CoManage) and can be requested (pulled in) by RPs when enabling a user's account (e.g., when the RP sets up a user’s allocation).

3. Upload via the RP’s upload service (using your ACCESS ID): Some RP’s have their own RP-specific web server that users can login to with their ACCESS ID and password and use features of the RP’s web site to upload their public key.

4. Upload via the RP’s upload service (using your RP ID): Some RP’s have their own RP-specific web server that users can login to with the RP ID and password they were given by the RP, and can then use features of the RP’s web site to upload their public key.

5. Upload via email: Some RPs ask that you email your public key to them.

6. Upload via SSO Hub (Only valid until Aug 31, 2022): Existing XSEDE user can use the XSEDE SSO Hub to copy their public key to an RP (via scp or cutting/pasting it into a terminal window logged into the RP).

Upload Details (for each approach above)

The following provides more detailed information and examples for each of the approaches. We also list RPs that currently support that approach. For more information about the RP’s specific requirements, please visit Logging in to Resource Providers.

<Details and screenshots about uploading your public key will appear here>

1. Upload via Open-On-Demand

An example of an RP that supports Open-On-Demand uploads is Anvil. The basic steps are: …

2. Upload via the ACCESS ID Management system (coming soon)

This services is still being developed. Please check back soon for updates.

3. Upload via RP upload service (ACCESS ID)

Describe an example RP

4. Upload via RP upload service (RP ID)

An example of an RP that supports its own upload service

5. Upload via email

Mention RPs that have sent out email to users telling them how to submit their public keys

6. Upload via SSO Hub (only until Aug 31, 2022)

Please see XSEDE announcements regarding the SSO Hub and how to login without the SSO hub.