GitHub authentication

Prerequisites

To authenticate, you need the following credentials:

• Bring your own OAuth 2.0 app: Client ID, Client secret, Organization, Account type.

To learn how to create your own OAuth 2.0 application, see the GitHub documentation.

Retrieve your GitHub credentials

1. Log in to your GitHub account.
2. Click on your profile image in the upper-right corner of the interface and select Your organizations.

3. The list of organizations is available under Organizations. You can choose any of the organization names displayed and use the exact name in the authentication screen of the GitHub connector.

   
   

   

   
   

If you encounter any issues with choosing the correct organization (in case of multiple organizations), contact your IT department.

If you are not part of an organization, you can easily create one from your GitHub interface:

1. Log in to your GitHub account.
2. Click your profile image in the upper-right corner of the interface and select Your organizations.
3. In the Organizations screen displayed, select New organizations.

4. Select your preferred plan and follow the on-screen instructions.

Note: For more information on how to create an organization and the plans available, visit the GitHub support website.

Add the GitHub connection

To create a connection to your GitHub instance, you need to perform the following steps:

1. Select Integration Service from Automation Suite.

2. From the Connectors list, select GitHub. You can also use the search bar to narrow down the connector.

3. Select the Connect to GitHub button.

4. Enter the required credentials, select the account type (Organization or Personal), and select Connect.

5. Your connection has been added.

Important: There is a limit of ten tokens that are issued for a user-application-scope combination. For details, see Authorizing OAuth Apps.

For more information on authenticating with GitHub, refer to the GitHub support website.

Permissions

The UiPath for GitHub connector asks for the following permissions:

• Full control of organization hooks
• Full control of repository hooks
• Read org and team membership, read org projects
• Full control of private repositories
• Update all user data