<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
GitHub Connector in Okta Workflows "not in org" Error
Workflows
Overview

When attempting to select the Organization/Repository in the various GitHub card(s), the error mentioned below may appear. This is generally due to issue(s) with the initial setup of the GitHub connection.

 

not in org

 

Applies To
  • GitHub Connector
  • Okta Workflows
  • Okta Classic Engine
  • Okta Identity Engine (OIE)
Cause

As part of creating the GitHub connection, the Organizations need to be selected for use in the various cards. Without this, the Organizations/Repositories will not be available, and the not in org error will appear.

Solution

There is an org-level grant during the initial connection in Workflows that allows granting access at the org level.

 

It is possible to force the workflows connector to go through the initial setup again by first logging in to the GitHub account used in the connector, navigating to Settings > Applications > Authorized OAuth Apps, and revoking the Okta Workflows app.

 

Then, go back to the connector, reauthorize it, and there should be the option to grant access to the orgs when scrolling down within the access details, and a list of the orgs will be visible:

 

Authorize Okta Preview Workflows

 

NOTE: For more information on authorization for the GitHub connector, please refer to the GitHub: Authorization documentation.

Loading
GitHub Connector in Okta Workflows "not in org" Error