Testing your Okta OIDC Configuration

Jamf Connect Documentation
Solution
Application
Jamf Connect
Content Type
Technical Documentation
Utilities & Services
ft:locale
en-US

After creating an authentication configuration with Jamf Connect, the integration can be tested via the Jamf Connect Configuration app to verify if users can successfully log in or if issues may be present.

Requirements

  • Access to the Jamf Connect Configuration application

  • A configured Jamf Connect application in Okta Identity Engine or Classic Engine

  • Credentials for a user assigned to your Jamf Connect application in Okta

  1. Open the Jamf Connect Configuration application, located in the Jamf Connect DMG file.
  2. Click the + icon to create a new configuration.
  3. In the Identity provider tab, select the following settings:
    1. Identity Provider: Okta OIDC
    2. OIDC client ID: The Client ID value located in the General tab of your Jamf Connect application in Okta.
    3. ROPG client ID: The same value as your OIDC client ID.
    4. Tenant: Your Okta tenant, such as example.okta.com.
  4. (Optional) If you are using Okta Classic engine and your Sign On Policy contains the Require multifactor action, navigate to the Hybrid Identity section of the Jamf Connect Configuration app.
    1. Enter Resource owner password into the ROPG success codes field.
  5. In the Connect tab, select the following settings:
    1. Navigate to the Authentication section.
    2. ROPG tenant: Your Okta tenant, such as example.okta.com.
  6. Click Test.
  7. Select OIDC.
  8. Enter the credentials for a user who is assigned to your Jamf Connect application in Okta.
  9. Upon a successful authentication, click Test again.
  10. Select ROPG.

A successful authentication will produce the following message: "Success. Your configuration seems to be working". An unsuccessful authentication will produce an error with details for troubleshooting.