CComposioHelp Center

Guide

Create Auth Config - Github

11 stepsAgent View (JSON)

Overview

Composio simplifies agent authentication by managing OAuth integrations across 1000+ toolkits. This workflow creates a GitHub OAuth 2.0 authentication configuration using Composio's secure, managed credentials—the recommended approach for getting started quickly. Once created, this auth config can be reused across multiple sessions and agents, eliminating the need to manage GitHub API keys directly. Composio handles credential security and token refresh automatically, allowing you to focus on agent logic rather than authentication infrastructure.

Before you begin

  • Access to dashboard.composio.dev with an active Composio account
  • GitHub account (not required to create the config, but will be needed when users authenticate through the OAuth flow later)
  • No custom GitHub OAuth app credentials required—Composio provides managed defaults

Step by step

1
ClickAuth Configs

Navigate to the Auth Configs section by clicking the 'Auth Configs' link in the dashboard navigation. This is where all authentication configurations for your agents are created and managed.

Step 1
2
ClickCreate

Click the 'Create' button to begin setting up a new authentication configuration.

Step 2
3
TypeSearch toolkits...

In the toolkit search field, type 'GitHub' to filter the available authentication options and locate the GitHub OAuth integration.

Tip. You can type partial matches—'GitHub', 'OAuth', or similar terms will return relevant results.
4
ClickGGitHubOAuth 2.0

Select 'GitHub OAuth 2.0' from the filtered results by clicking on it. This option enables secure OAuth 2.0-based login for your agents when they need to authenticate with GitHub.

Step 4
5
ClickNext

Click the 'Next' button to proceed to the authentication method selection screen.

Step 5
6
ClickSecure, user-friendly login via OAuth 2.0 authorization flow

Review the OAuth 2.0 authentication method description ('Secure, user-friendly login via OAuth 2.0 authorization flow'). This confirms you are configuring the correct authentication flow type.

Step 6
7
ClickOAuth 2.0Secure, user-friendly login via OAuth 2.0 authorization flow

Select the OAuth 2.0 radio button to confirm this is the authentication flow method you want to use for GitHub authentication.

Tip. OAuth 2.0 is the recommended and most secure method for GitHub authentication with Composio agents.
Step 7
8
ClickComposio Managed Recommended Get started quickly with Composio's secure defaults. You can switch to your own credentials anytime.

Review the Composio Managed credentials option, which is recommended for getting started. This option uses Composio's secure defaults and allows you to switch to custom credentials later if needed.

Tip. Composio Managed is marked as 'Recommended' and provides automatic token refresh and secure credential storage without requiring you to manage GitHub API keys directly.
Step 8
9
ClickComposio ManagedRecommendedGet started quickly with Composio's secure defaults. You can switch to your own credentials anytime.

Select the Composio Managed radio button to use Composio's managed credentials for this GitHub OAuth 2.0 configuration. This is the fastest way to get your agents authenticating with GitHub.

Step 9
10
ClickCreate Auth Config

Click the 'Create Auth Config' button to finalize and save your GitHub OAuth 2.0 authentication configuration with Composio-managed credentials.

Tip. After clicking, you may be redirected or see a confirmation. The auth config is now available for use in any agent or session you create.
Warning. Ensure you have selected both OAuth 2.0 as the method and Composio Managed as the credentials source before clicking, or you may need to repeat the configuration.
Step 10
11
TypeSearch toolkits...

The toolkit search field may clear or remain visible on the confirmation screen. You can now use this field to search for other toolkits or auth configs, or navigate away from this screen to use your new GitHub OAuth 2.0 config.

Tip. Your newly created GitHub auth config is now ready to be assigned to agents or sessions. You can return to the Auth Configs section to view, edit, or delete it.

Confirm it worked

  1. 1You see the auth config listed in the Auth Configs section of the dashboard
  2. 2The GitHub OAuth 2.0 config displays with 'Composio Managed' badge indicating managed credentials are in use
  3. 3The config status shows as active and ready to use with agents and sessions

Common issues

Keep reading

Auth.js | Configuring Github

Auth.js | Configuring GithubSkip to content The Auth.js project is now part of Better Auth. Guides Configuring GitHub for OAuth # OAuth with GitHub In this tutorial, we’ll be setting up Auth.js in

authjs.dev

Next.js + Auth.js v5 - React SME Cookbook

Next.js + Auth.js v5 - React SME Cookbook authauthjsnextauthoauthgithubmiddlewaresession # Next.js + Auth.js v5 Add authentication to a Next.js 15 app with Auth.js v5 (formerly NextAuth), including

reactdevelopers.org

Basic GitHub OAuth Authentication with Next.js and next-auth | GoGrow Blog

Basic GitHub OAuth Authentication with Next.js and next-auth | GoGrow Blog # Basic GitHub OAuth Authentication with Next.js and next-auth Learn to set up GitHub OAuth in Next.js with next-auth, cove

gogrow.dev