Configure a Source Control Credential
Add your token or key and your Namirasoft applications can connect to GitHub or GitLab. The steps below show you how to get and enter each one.
Create the credential
In the Namirasoft Credential Console, open Source Control › GitHub, then click Create.
Name it and add the server
Give the credential a Name you will recognize. Set the Host to github.com (or your GitHub Enterprise host), and enter your GitHub Username.
Choose the GitHub Type
The type sets how you authenticate, and the fields change to match. Pick one:
Enter the values for your type
Password uses your GitHub account password to sign in.
- Enter your GitHub account Password.
PAT Classic is a token you generate with broad account scopes.
- Enter your Personal Access Token.
PAT Fine Grained is a token scoped to specific repositories and permissions.
- Enter your Fine Grained Token.
An OAuth App provides four values from your registered app.
- Enter the Client ID and Client Secret.
- Enter the Access Token and Refresh Token.
A GitHub App authenticates with its installation and a signed token.
- Enter the Installation ID.
- Enter the JWT and Token.
SSH signs in with a key pair instead of a password or token.
- Enter your SSH Public Key and Private Key.
Describe and save
Optionally add a Description of what the credential is for, then click Apply.
Create the credential
In the Namirasoft Credential Console, open Source Control › GitLab, then click Create.
Name it and add the server
Give the credential a Name you will recognize. Set the Host to gitlab.com (or your self managed host), and enter your GitLab Username.
Choose the GitLab Type
The type sets how you authenticate, and the fields change to match. Pick one:
Enter the values for your type
Password uses your GitLab account password to sign in.
- Enter your GitLab account Password.
PAT is a token you generate instead of your password.
- Enter your Personal Access Token.
An OAuth App provides four values from your registered app.
- Enter the Client ID and Client Secret.
- Enter the Access Token and Refresh Token.
SSH signs in with a key pair instead of a password or token.
- Enter your SSH Public Key and Private Key.
Describe and save
Optionally add a Description of what the credential is for, then click Apply.
Source Control FAQs
Answers to common questions about setting up source control credentials.
1. Which method should I choose if I am not sure?
You choose a personal access token for most cases, because it keeps your account password out of the credential. You use SSH if you prefer key based access.
2. What happens when my token expires?
Your authorized applications read the token from this one credential each time they connect, so you replace an expired token in one place and they all use the new one automatically. If a token expires and you do not update it, the connections stop working.