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.
Choose your platform to see its setup steps:
Step 1: Create the Credential
- Open the Namirasoft Credential Console and go to Source Control, then GitHub.
- Click Create to start a new credential.
Step 2: Enter the Name and Server Details
- Enter a Name you will recognize.
- The Host is your GitHub server (github.com, or your Enterprise host), and the Username is your GitHub account.
- Type each into its Host and Username field.
Step 3: Choose the GitHub Type
- The GitHub Type sets how you authenticate, and the fields change to match your choice.
- Select Password, PAT Classic, PAT Fine Grained, OAuth App, GitHub App, or SSH in the GitHub Type field.
Step 4: Enter the Values for Your Type
Choose your GitHub type to see its fields.
Password uses your GitHub account password to sign in.
- Enter your GitHub account Password in its field.
PAT Classic is a token you generate with broad account scopes.
- Enter your Personal Access Token in its field.
PAT Fine Grained is a token scoped to specific repositories and permissions.
- Enter your Fine Grained Token in its field.
An OAuth App provides four values from your registered app.
- Enter the Client ID and Client Secret in their fields.
- Enter the Access Token and Refresh Token in their fields.
A GitHub App authenticates with its installation and a signed token.
- Enter the Installation ID in its field.
- Enter the JWT and Token in their fields.
SSH signs in with a key pair instead of a password or token.
- Enter your SSH Public Key and Private Key in their fields.
Step 5: Add a Description and Save
- Optionally note what the credential is for in the Description field.
- Click Apply to save.
Step 1: Create the Credential
- Open the Namirasoft Credential Console and go to Source Control, then GitLab.
- Click Create to start a new credential.
Step 2: Enter the Name and Server Details
- Enter a Name you will recognize.
- The Host is your GitLab server (gitlab.com, or your self managed host), and the Username is your GitLab account.
- Type each into its Host and Username field.
Step 3: Choose the GitLab Type
- The GitLab Type sets how you authenticate, and the fields change to match your choice.
- Select Password, PAT, OAuth, or SSH in the GitLab Type field.
Step 4: Enter the Values for Your Type
Choose your GitLab type to see its fields.
Password uses your GitLab account password to sign in.
- Enter your GitLab account Password in its field.
PAT is a token you generate instead of your password.
- Enter your Personal Access Token in its field.
An OAuth App provides four values from your registered app.
- Enter the Client ID and Client Secret in their fields.
- Enter the Access Token and Refresh Token in their fields.
SSH signs in with a key pair instead of a password or token.
- Enter your SSH Public Key and Private Key in their fields.
Step 5: Add a Description and Save
- Optionally note what the credential is for in the Description field.
- Click Apply to save.
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.