Jamf Connect can use the Okta Authentication API to configure primary Jamf Connect tasks for users, such as the following:
Cloud authentication to a local account
Password syncing
Signing in users to Okta
To learn more about this API, see the Authentication API developer documentation from Okta.
Jamf Connect can also use the OpenID Connect protocol to enable support for the following:
An authentication experience via the login window and Self Service+ which displays a webview to your organization's Okta sign-in screen, rather than a native macOS user interface.
New compatibility with Jamf Connect features that are only available for OpenID Connect authentication (not supported with the authentication API), such as passthrough authentication.
User experience may vary between Authentication API and OpenID Connect
Jamf recommends deploying changes in a test environment to identify if a full transition is right for your organization. To learn more about OpenID Connect with Okta, see the OpenID Connect & OAuth 2.0 API developer documentation from Okta.