Authorization
When you add a GitHub card to a flow for the first time, you'll be prompted to configure the connection. This will enable you to connect your GitHub account, save your account information, and reuse the connection in new flows that include GitHub. The GitHub connector uses OAuth protocol.
You can create multiple connections and manage them from your Connections page.
OAuth app access restrictions
When a GitHub organization is created, OAuth App access restrictions are enabled by default. If these restrictions are enabled in your organization, you must disable them to create a connection and authorize Workflows to access the organization's resources. See Disabling OAuth App access restrictions for your organization.
When OAuth App access restrictions are disabled for an org, any member of the org automatically authorizes OAuth App access to the organization's private resources when they approve an application for use.
Create a new GitHub connection in Workflows
Before you begin
-
Okta Workflows admin credentials
-
GitHub credentials
Supported scopes
-
admin:org
-
user
-
repo
-
delete_repo
-
admin:repo_hook
Start this task
-
There are two ways that you can create a new connection:
-
Add a GitHub card to your flow and click New Connection.
-
Open the Connections tab in the Workflows platform. Click New Connection, click GitHub.
-
-
In the Connection Nickname field, enter the display name that you want to appear in your list of connections. This is useful if you plan to create multiple GitHub connections to share with your team.
-
Click Create. The Single sign-on to your organizations dialog appears.
-
Click Authorize beside one or more GitHub organizations to authenticate for use with this connection. Click Continue.
-
The Authorize Okta Workflows window appears (or Authorize Okta Preview Workflows, if working in an Okta preview org). This lists the scopes that the connection will use. It also lists organizations that Workflows can access. You can grant access to an organization that you didn't previously authorize by clicking Grant beside the organization. Click Authorize workflows-apps.
-
Enter your GitHub password. Click Confirm password.
Delete a GitHub connection in Workflows
You can delete individual GitHub connections to deauthorize the GitHub application connector.
Before you begin
-
Okta Workflows admin credentials
Delete a GitHub connection in Workflows
-
In the Okta Workflows Console, go to Connections.
-
Click Delete next to the connection you want to delete. The Delete Connection dialog appears.
-
On the window, click Confirm.
The connection is now deleted.
Troubleshooting connection issues
Consult the following information when you are experiencing Github connection issues in Workflows.
Third Party Access
If you cannot view your organization or you are unable to receive data from it, make sure that you have granted third-party access to the Workflows OAuth application.
- Go to Github.
- In the top-right corner of GitHub, click your profile photo, then click Your organizations.
- Next to the organization, click Settings.
- Next to Settings, click Third-party access.
- Next to the application you'd like to approve, click Review.
- After you review the information about the requested application, click Grant access.
Authorize and grant access to your application
Authorize a Github application to allow your application to retrieve information about your Github account.
- Go to .
- Select an application.
- Select Grant, to grant access to your application.
Recreate a Connection
If your organization's settings have changed, you need to reauthorize your organization.
- In the Admin Console, go to .
- Under Connections, click New Connection.
- Select a connector.
- In the Single sign-on to your organization box, click Authorize.
- Click Continue.
- Enter your credentials.
- Click Sign in.