GitHub

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 log in to github navigate to your account settings select developer settings choose either personal access tokens or github apps depending on your authentication method generate a new token with the required scopes 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 log in to turbine from the left hand navigation pane, click orchestration and click assets click the plus icon to create a new asset select github from the asset type list fill in the asset settings and asset input fields as shown configuration parameters true 220,220,221 unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type 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