GitHub Enterprise Cloud - Organization API authentication flow fails with the following error visible in the Okta dashboard:

Error authenticating: No results for users returned"
 

Okta is authenticating using an account with admin privileges on the GitHub side and has been authorized to connect to the GitHub account, as shown below:
 

• GitHub Enterprise Cloud - Organization
• Provisioning
• API Error

This error Error authenticating: No results for users returned appears because SAML SSO is not enabled for GitHub Enterprise Cloud - Organization. This is one of the prerequisites for integrating GitHub Enterprise Cloud - Organization with Okta.

The same error could occur if the service account on GitHub that was used to set up the Provisioning is no longer active (deleted or disabled/deactivated).

1. Go to Okta Admin Console and navigate to Applications > GitHub Enterprise Cloud - Organization > Sign On. Follow the instructions in the View SAML Setup Instructions link to enable SAML within the GitHub organization account.

2. Log in to GitHub Enterprise Cloud - Organization as the administrator of the GitHub organization for which SAML is desired. Go to organization settings. Select Authentication security, then in the SAML single sign-on section, do the following:

   1. Check the Enable SAML authentication box.
   2. Copy and paste the Sign on URL, Issuer, and Public Certificate from the View SAML Setup Instructions link.
   3. Before enabling, test the SAML SSO configuration, click Test SAML Configuration.
   4. Once the Test Configuration is successful, click the Save button.

3. Go to the Okta Admin Console and navigate to Applications > GitHub Enterprise Cloud—Organization > Provisioning > Integration. Then click the Edit button.

4. Click Authenticate with GitHub Enterprise Cloud - Organization to generate a token.

5. The GitHub Sign in window will open. Enter the GitHub Admin account credentials and click the Sign in button.

6. If acceptable, click on Authorize OktaOAN to Grant access to the organization account.

7. A message confirming successful authentication will be seen. Click Save.

NOTE: Ensure the GitHub service account used to set up the provisioning is active (not deleted, nor disabled/deactivated). 

If the issue persists, please contact GitHub support for more details and steps on how to resolve this error.

Related References

• GitHub Enterprise Cloud - Organization: Configuration Guide