Okta GitHub Enterprise Managed User API Authentication Fails With Error: "No Results for users returned"

The Okta GitHub Enterprise Managed User API authentication flow fails when Security Assertion Markup Language (SAML) Single Sign-On (SSO) is not enabled for the GitHub Enterprise Managed User. Enable SAML SSO in GitHub and reconfigure the API integration in Okta to resolve the issue. When this issue occurs, Okta displays the following error in the dashboard:

Error authenticating: No results for users returned

• Okta Identity Engine (OIE)
• Okta Classic Engine
• GitHub Enterprise Managed User
• Provisioning
• API

This error appears because SAML SSO is not enabled for the GitHub Enterprise Managed User.

1. Go to the Okta Admin Console and navigate to Applications > Applications.
2. Select the GitHub Enterprise Managed User application.
3. Choose the Assignments tab and assign the application to the setup user account.
4. Navigate to the Sign On tab and select More details under the SAML 2.0 section.
5. Note the Sign on URL, Issuer, and Signing certificate values.
6. Sign in to GitHub Enterprise with managed users.
7. Use the noted details from Okta to configure SAML single sign-on for Enterprise Managed Users in GitHub. Follow the steps in Configuring SAML single sign-on for Enterprise Managed Users.
8. Return to the Okta Admin Console and navigate to Applications > Applications.
9. Select the GitHub Enterprise Managed User application.
10. Navigate to the Provisioning tab and select Integration.
11. Choose Edit.
12. Enter the personal access token belonging to the setup user in the API Token field.
13. Select Test API Credentials. Okta displays a verification message at the top of the screen if the test is successful.
14. Select Save.