GitLab Console Guide

This page provides a complete guide to the GitLab section of the Namirasoft Credential Console. GitLab credentials support several authentication methods (Password, Personal Access Token, SSH, and OAuth), so you can connect to GitLab SaaS or a self managed instance in the way that fits your setup.

What Is GitLab?

GitLab is a platform for hosting Git repositories and managing the full software development lifecycle, including code review, issues, and continuous integration. It is available as a cloud service and as a self managed installation.

 

Namirasoft Credential connects to GitLab using the authentication method you choose, so authorized Namirasoft applications can access your GitLab data without storing your secrets in plain form.

 

Why Secure Credential Management Matters

GitLab credentials, such as passwords, tokens, and private keys, can grant access to your repositories and account data. If they are exposed in logs, configuration files, or shared machines, they can be misused. For this reason every credential must be encrypted and access controlled, exactly like a password.

 

Overview of GitLab Fields and Options

The sections below explain every field in the GitLab credential form. The fields shown depend on the GitLab Type you select.

• ID (String): This is the unique identifier automatically generated by Namirasoft Credential when a GitLab 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 GitLab 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 credential, such as GitLab Production or CI Bot. It helps you and your team recognize which credential is which and has no impact on authentication itself.

• Host (String): This is the GitLab server that Namirasoft connects to. For GitLab SaaS, enter gitlab.com. For a self managed instance, enter the address you use to reach it, such as gitlab.company.com. You can usually find this value in your browser address bar or from your GitLab administrator.

• Username (String): This is the username of the GitLab account that Namirasoft authenticates with, used together with the method you select below. It is the handle shown on your GitLab profile, not your email address.

• GitLab Type (Enum): This selects how Namirasoft authenticates to GitLab. Choose Password, PAT (personal access token), SSH (key pair), or OAuth. The fields shown below change based on this selection, so you only complete the values your chosen method requires. The values you enter are encrypted and stored in Namirasoft Secret.

• Password: Authenticate with your GitLab username and password.

 

• • Password (String): This is the password for the GitLab account named above. Enter the password that account signs in with. If the account uses two factor authentication, password access may be blocked; in that case use the PAT method instead.

 

How to Get Your Password?

 

• Use the password you sign in to GitLab with
• If your account uses two factor authentication, password access may be blocked, so choose the PAT type instead
• Enter the value exactly as it is

 

 

• PAT: Authenticate with a personal access token, used in place of your password.

 

• • PAT Token (String): This is the personal access token generated in your GitLab account. It grants access based on the scopes you select and is used in place of your password. Paste it exactly as GitLab provided it.

 

How to Create a GitLab Personal Access Token?

 

• Sign in to GitLab, click your avatar, then choose Edit profile
• In the left sidebar, select Access tokens
• Set a name, an optional expiration, and only the scopes Namirasoft needs
• Click Create personal access token
• Copy the token immediately (it is shown only once)
• Paste it into the PAT Token field and save

 

 

• SSH: Authenticate with an SSH key pair, using a public and private key.

 

• • SSH Public Key (String): This is the public half of your SSH key pair, the same key you add to your GitLab account. It usually begins with ssh-ed25519 or ssh-rsa.

 

• • SSH Private Key (String): This is the private half of your SSH key pair, which proves your identity to GitLab. Paste the full contents of the private key file, including the header and footer lines, and keep it secret.

 

How to Generate an SSH Key Pair?

 

• Open a terminal (Linux, macOS, or Windows 10 and later)
• Run:

 

ssh-keygen -t ed25519

 

• This creates a private key (id_ed25519) and a public key (id_ed25519.pub)
• Paste the public key contents into the SSH Public Key field
• Paste the private key contents into the SSH Private Key field
• In GitLab, open Edit profile, then SSH Keys, and add the same public key

 

 

• OAuth: Authenticate through a registered GitLab OAuth application, using a client ID, client secret, and tokens.

 

• • OAuth Client ID (String): This is the public identifier issued to your GitLab OAuth application when you register it. It identifies your application during the OAuth flow and is not secret on its own.

 

• • OAuth Client Secret (String): This is the confidential secret issued with your OAuth application. It is used together with the client ID to authenticate your application and must be kept private.

 

• • OAuth Access Token (String): This is the token used to make authorized requests to GitLab on behalf of the user.

 

• • OAuth Refresh Token (String): This is the token used to obtain a new access token when the current one expires, so access continues without re authorizing.

 

How to Get Your GitLab OAuth Credentials?

 

• In GitLab, open Edit profile, then Applications
• Add a new application, set a name and redirect URI, and select the scopes Namirasoft needs
• Save to get the Client ID and Client Secret
• Complete the authorization flow to obtain the Access Token and Refresh Token
• Paste each value into its matching field

 

 

• Description (String): This is an optional text field where you can explain the purpose or usage of the GitLab credential, such as which repositories it can access or what team uses it. 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 GitLab credential 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 GitLab credential record was most recently modified. It helps you track when the credential was last maintained.