---
title: GitHub
slug: authentication-guides/github
docTags: 
createdAt: 2026-01-19T20:59:08.629Z
---

# Introduction

This guide tells you how to authenticate the GitHub connector in Swimlane using HTTP Bearer Authentication.
You will generate a GitHub authentication token, collect the required information, and configure the connector in Swimlane.

# Prerequisites

## GitHub Access Requirements

You must have access to a GitHub account with permissions to generate authentication tokens and access repositories, organizations, or user resources required for your automation use cases.

## Required Credentials

During setup, you will collect:

- GitHub API URL
- Personal Access Token or JWT-Token

# Authentication Methods Overview

The GitHub connector supports the following authentication method:
**HTTP Bearer Authentication: **This method uses a GitHub Personal Access Token or a JWT-Token to authenticate API requests.

# GitHub Token Setup

Take the following steps to generate an authentication token in GitHub:

1. Log in to GitHub.
2. Navigate to your account settings.
3. Select Developer settings.
4. Choose either Personal access tokens or GitHub Apps depending on your authentication method.
5. Generate a new token with the required scopes.
6. Copy and securely store the token. This value will be used when configuring the Swimlane asset.

# Connector Configuration in Swimlane

Take the following steps to configure the GitHub connector asset in Swimlane:

1. Log in to Turbine.
2. From the left-hand navigation pane, click **ORCHESTRATION **and click **Assets**.
3. Click the **plus **icon to create a new asset.
4. Select GitHub from the **Asset Type** list.Fill in the **Asset Settings** and **Asset Input** fields as shown:

**Configuration Parameters**

| **Parameter** | **Description**                                                | **Requirement** |
| ------------- | -------------------------------------------------------------- | --------------- |
| url           | GitHub API endpoint URL                                        | Required        |
| token         | Personal Access Token or JWT-Token with sufficient permissions | Required        |
| verify\_ssl   | Enable or disable SSL certificate verification                 | Optional        |
| http\_proxy   | Optional proxy configuration                                   | Optional        |

![](https://api.archbee.com/api/optimize/n8uUzk0MM4uC57-zlHNtY/OnJM25IIVoFefv-ZlXDZF_image.png)

# Troubleshooting

If authentication fails:

- Ensure the token is valid and has not expired.
- Verify the token has the required scopes or permissions.
- Confirm the GitHub API URL is correct.
- Check SSL and proxy settings if applicable.

You have successfully authenticated the GitHub connector in Swimlane.