Git

Access git servers securely through Hoop using SSH. This integration enables secure git operations, repository management, and git server resource access through the Hoop proxy with complete audit trails and access controls. Works with GitHub, GitLab, Gitea, Forgejo, and any SSH-based git server.

Before you start

To get the most out of this guide, you will need to:

• Either create an account in our managed instance or deploy your own hoop.dev instance
• You must be your account administrator to perform the following commands

Features

The table below outlines the features available for this type of connection.

• Native - Accessible via a native connection using hoop as proxy protocol to the resource.
• One Off - This term refers to accessing the resource from Hoop Web Console.

Feature	Native	One Off	Description
TLS Termination Proxy			The local proxy terminates the connection with TLS, enabling the connection with the remote server to be TLS encrypted.
Audit			The gateway stores and audits the queries being issued by the client.
Data Masking (Google DLP)			A policy can be enabled to mask sensitive fields dynamically when performing queries in the database.
Data Masking (MS Presidio)			A policy can be enabled to mask sensitive fields dynamically when performing queries in the database.
Guardrails			An intelligent layer of protection with smart access controls and monitoring mechanisms.
Credentials Offload			The user authenticates via SSO instead of using database credentials.
Interactive Access			Interactive access is available when using an IDE or connecting via a terminal to perform analysis exploration.

SSH Key Setup

To access git servers through Hoop, you need an SSH key registered with your git server account. This works with GitHub, GitLab, Gitea, Forgejo, and any SSH-based git server.

Generate SSH Key (if you don’t have one)

ssh-keygen -t rsa -b 4096 -f ~/.ssh/git_key -N ""

Register Key with Your Git Server

GitHub:

• Go to GitHub Settings → SSH and GPG keys → New SSH key
• Paste your public key
• Give it a name (e.g., “Git Access”)
• Click “Add SSH key”

GitLab:

• Go to GitLab Settings → SSH Keys
• Paste your public key
• Set expiration date if needed
• Click “Add key”

Gitea/Forgejo:

• Go to Settings → SSH/GPG Keys
• Click “Add Key”
• Paste your public key

Display Your Public Key

cat ~/.ssh/git_key.pub