In order to limit access in Okta, a specific Jamf Connect application must be created and configured via Okta Classic Engine or Identity Engine.
Requirements
Access to your organization's Okta Identity Engine or Okta Classic Engine admin console.
An existing Okta app integration with OpenID Connect 2.0.
- Log in to the Okta Admin Console.
- Click Applications.
- Click Create App Integration.
- Do the following in the Create a new app integration window:
- Select OIDC - OpenID Connect as the sign-in method.
- Select Native Application as the application type.
- Click Next.
- Configure the following app integration settings:
- Enter a name for your app, such as Jamf Connect - Access or Jamf Connect - Admin Rights, in the Application name field.
- (Optional) Upload an application logo.
- Select the Implicit (hybrid) code grant types.
- Enter the following text in the Sign-in redirect URIs field: https://127.0.0.1/jamfconnect
- Remove the Sign-out redirect URIs field by clicking the X next to the text field.
- (Optional) Assign users to the Jamf Connect application or select Skip group assignment for now.
- Click Save.
- Navigate to the Okta API Scopes tab and locate okta.users.read.
- Click Grant.
- Navigate to the Sign in tab and record the value of the Client ID. Save this value to be used later.
You can now configure an authentication policy with Okta Identity Engine or a Sign On policy with Okta Classic Engine.