SSH Console Guide

This page provides a clear and complete guide to the SSH section of the Namirasoft Credential Console. It explains what SSH access is, how Namirasoft Credential stores your SSH details securely, and every field in the SSH credential form.

What Is SSH?

SSH (Secure Shell) is a protocol for connecting to and managing a server over an encrypted connection. It is widely used to run commands on remote machines and to create secure tunnels that let applications reach services inside a private network.

 

In Namirasoft Credential, an SSH credential lets authorized applications connect to your server, either directly or as a secure tunnel to reach databases and other services that are not exposed to the public internet.

 

Why Secure SSH Credential Management Matters

SSH credentials, especially private keys, grant direct access to your servers. Storing them in plain files, sharing them between machines, or pasting them into application configuration increases the risk of:

 

• Accidental exposure of private keys in logs or repositories

 

• Unauthorized server access if a key or password is leaked

 

• Loss of control when credentials are shared across multiple machines or teams

 

For this reason, SSH passwords and private keys must be encrypted and access controlled, exactly like any other secret.

 

Overview of SSH Fields and Options

The sections below explain every field in the SSH credential form.

• ID (String): This is the unique identifier automatically generated by Namirasoft Credential when an SSH record is created. You do not enter or modify this value. It is used internally for tracking, linking, and referencing the entry across the Namirasoft ecosystem.

• User ID (Namirasoft Account’s ID): This is the unique ID assigned to the Namirasoft Account that created the SSH record. It serves as a link between the credential and the user who owns or manages it.

• Workspace ID (Namirasoft Workspace’s ID): This refers to a workspace created in the Namirasoft Workspace app, which allows users to organize credentials by project, environment, or team. The workspace name is displayed along with the ID, and it links back to the Namirasoft Workspace app where the workspace details can be viewed.

• Name (String): This is a human friendly label you choose to identify the SSH credential, such as Production Server or Bastion Host. It helps you and your team recognize which credential is which and has no impact on authentication itself.

• Type (Enum): This selects the authentication method your server accepts. Choose Password to authenticate with a username and password, or Private Key to authenticate with a key pair. The fields shown in the form change based on this selection. The values you enter are encrypted and stored in Namirasoft Secret.

• Host (String): This is the network address of the server that the Namirasoft application will connect to. It is typically a domain name (such as server.company.com) or an IP address (such as 192.168.1.10). You can usually obtain this value from your server administrator, hosting provider, or infrastructure documentation.

• Port (Integer): This is the network port used by the SSH service on the server. The default SSH port is 22, although some environments use a different port for security or operational reasons. You can usually find the correct port in your server configuration or from the administrator responsible for the server.

• Username (String): This is the account name used to log in to the server through SSH. Common examples include service accounts, administrator accounts, or operating-system user accounts created on the server. You can obtain this value from the server administrator or from the instructions provided with the server.

• Password (String): This is the password for the SSH user account on the server. Enter the correct password for the same user account entered above.

• Private Key (String): This is the private portion of an SSH key pair used to authenticate to the server. It is typically stored in a text file and begins with a line such as -----BEGIN OPENSSH PRIVATE KEY----- or -----BEGIN RSA PRIVATE KEY-----. Paste the entire contents of the file, including the header and footer lines. The corresponding public key must already be installed on the target server.

ssh-keygen -t ed25519

• Private Key Passphrase (String): This is the optional password used to protect the private key file. Enter the passphrase that was specified when the key pair was created. If the private key was generated without a passphrase, leave this field empty.

• Fingerprint (String): This is the unique identifier of the server’s SSH host key. It is used to verify that a Namirasoft application is connecting to the correct server and helps prevent impersonation attacks. It typically appears as a short string such as SHA256:uXJ3s8A.... You can obtain it from your server administrator, hosting provider, or by following the steps below.

ssh-keyscan <hostname> | ssh-keygen -lf -

• Description (String): This is an optional text field where you can explain the purpose or usage of the credential, such as which server it connects to or what environment it belongs to. Adding a description is helpful when working with multiple credentials in a shared workspace.

• Created At (DateTime): This shows the exact date and time when the SSH record was first created. This value is automatically set when you create the record and does not change over time.

• Updated At (DateTime): This shows the exact date and time when the SSH record was most recently modified. It helps you track when the credential was last maintained.