wiki.chpc.ac.za

User Tools

Site Tools

You are here: start » guide » sshkeys
Trace:
guide:sshkeys

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
guide:sshkeys [2026/06/18 22:21]
ccrosby Removed the Linux section to transfer it to a daughter page 		guide:sshkeys [2026/07/14 12:47] (current)
ccrosby Updated link to updated video
Line 12: Line 12:
 This is the process for logging into Lengau for the first time once services have been restored: This is the process for logging into Lengau for the first time once services have been restored:
  
-  - Login to the CHPC User Portal using your username and password.+  - Login to the [[https://users.chpc.ac.za/|CHPC User Portal]] using your username and password.
   - Complete MFA verification using the 6-digit code sent to your email (valid for 2 hours).   - Complete MFA verification using the 6-digit code sent to your email (valid for 2 hours).
-  - Download and configure your unique VPN profile, then connect to the CHPC VPN.+  - [[https://users.chpc.ac.za/vpn/|Configure and download]] your unique VPN profile, then connect to the CHPC VPN.
   - Create your SSH keys (if none exist) and copy the contents of public key to a text file.   - Create your SSH keys (if none exist) and copy the contents of public key to a text file.
-  - SSH to Lengau using your CHPC username. +  - Load the contents of the public key file onto the cluster through the [[https://users.chpc.ac.za/ssh-user/|ssh-keys management page]] on the user portal. 
-  - Enter the password when prompted ( can reset on the user portal ) +  - SSH to Lengau using your CHPC username.  If you have not loaded the keys at the previous step, you will be prompted to do so now at the login prompt. 
-  - On first login, from step 4 copy and paste your SSH public key into the terminal when requested. +
-  - Disconnect and login again — future access will use SSH key authentication.+
  
  
Line 28: Line 27:
   - It is very easy to generate the key pair from a command line.  Using the menu interface in a GUI-based application is slightly more complicated.   - It is very easy to generate the key pair from a command line.  Using the menu interface in a GUI-based application is slightly more complicated.
   - Once you have an appropriate key pair, you can use the same private key on different workstations, different operating systems and different ssh clients - it is simply a matter of providing the client with the appropriate key.     - Once you have an appropriate key pair, you can use the same private key on different workstations, different operating systems and different ssh clients - it is simply a matter of providing the client with the appropriate key.  
-  - Commandline ssh clients generally store the keys in the $HOME/.ssh directory or its equivalent +  - Command-line ssh clients generally store the keys in the $HOME/.ssh directory or its equivalent. 
-  - ssh clients with GUIs, such as MobaXterm or BitVise, need to be configured appropriately +  - ssh clients with GUIs, such as MobaXterm or BitVise, need to be configured appropriately (free versions are fine). 
-  - Windows users can choose from a wide range of ssh clients.  CHPC staff members prefer MobaXterm and prefer not to support WinSCP.  If you need software that can offer more powerful menu-based file transfers as well as a command line terminal, consider BitVise.+  - Windows users can choose from a wide range of ssh clients.  CHPC staff members prefer MobaXterm and prefer not to support PuTTY or WinSCP.  If you need software that can offer more powerful menu-based file transfers as well as a command line terminal, consider BitVise. 
 +  - In Unix-like operating systems like Linux or Cygwin, the permissions of the key files and authorized_keys are important.  The user must have read and write access to these files and there must be no other permissions.  The permission of a file such as authorized_keys can be set correctly with ''chmod 0600 authorized_keys''. 
  
  
Line 43: Line 43:
  
  
-====macOS==== +==== Video tutorial for Windows users ==== 
-  - Open Terminal on your Mac. +The MobaXterm command line method illustrated in [[https://youtu.be/Fq6xT-KjlQ0|this video]] is nearly identical to the method used for Linux and MacOS.
-  - Generate a new key: <code>ssh-keygen -t ed25519 -C "your_username@lengau"</code> +
-  - Press Enter to accept the default file location. +
-  - Keep the private key safe in: <code>~/.ssh/id_ed25519</code> +
-  - Show your public key: <code>cat ~/.ssh/id_ed25519.pub</code> +
-  - If you generated the key on your computer, copy the contents of your public key file (the file name with extension ''.pub'') and paste it on the login node when you register the key.+
  
  
Line 81: Line 76:
  
  
-=====FAQ=====  
- 
-FAQ 1: Enrollment loop: “I enrolled already, but it keeps opening First Login Enrollment" 
- 
-  *User completed **HPC First Login Enrollment** once.  
-  *On the next login attempt, the enrollment wizard opens again. 
-  *It detects they are **already enrolled** and **auto-closes**. 
-  *User never reaches a normal cluster session. 
- 
-Fix: Log helpdesk ticket to manually resolve the issue.  
- 
-FAQ 2: “Lengau hanging is is it just for me?" 
- 
-Fix: Check network 
  
/app/dokuwiki/data/attic/guide/sshkeys.1781814074.txt.gz · Last modified: 2026/06/18 22:21 by ccrosby

Page Tools

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial-Share Alike 3.0 Unported
CC Attribution-Noncommercial-Share Alike 3.0 Unported Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki