From 8778890178368d0ffdfab83821f2a116398e73bd Mon Sep 17 00:00:00 2001
From: Jan Siwiec <jan.siwiec@vsb.cz>
Date: Mon, 11 Mar 2024 09:25:49 +0100
Subject: [PATCH] Update ssh-keys.md

---
 .../ssh-keys.md                               | 20 +++++++++++++++++++
 1 file changed, 20 insertions(+)

diff --git a/docs.it4i/general/accessing-the-clusters/shell-access-and-data-transfer/ssh-keys.md b/docs.it4i/general/accessing-the-clusters/shell-access-and-data-transfer/ssh-keys.md
index dd8bd7c84..070878011 100644
--- a/docs.it4i/general/accessing-the-clusters/shell-access-and-data-transfer/ssh-keys.md
+++ b/docs.it4i/general/accessing-the-clusters/shell-access-and-data-transfer/ssh-keys.md
@@ -14,6 +14,26 @@ local $ ssh-keygen -C 'username@organization.example.com' -f additional_key
 By default, your private key is saved to the `id_rsa` file in the `.ssh` directory
 and your public key is saved to the `id_rsa.pub` file.
 
+## Adding SSH Key to your linux system SSH Agent
+
+1. Check if SSH Agent is running:
+
+    ```
+    eval "$(ssh-agent -s)"
+    ```
+
+1. Add the key to SSH Agent:
+
+    ```
+    ssh-add ~/.ssh/name_of_your_ssh_key_file
+    ```
+
+1.  Verify the key Added to SSH Agent:
+
+    ```
+    ssh-add -l
+    ```
+
 ## Managing Your SSH Key
 
 To manage your SSH key for authentication to clusters, see the [SSH Key Management][1] section.
-- 
GitLab