<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
Okta Workflows - February 2024 - Jamf Pro Classic API Connector Migration Guide
Okta Classic Engine
Okta Identity Engine
Workflows
Overview

Jamf is deprecating username and password-based basic authentication of Jamf Pro Classic API. After March 31st, 2024, the OAuth 2.0 Resource Owner Password Credentials authorization (Bearer Token) will be supported.

This change is backward compatible with the existing basic authentication, and the Jamf Pro Classic API Workflows connector will continue working.

Okta is releasing a smooth update to utilize the existing username and password basic authentication inside the connector to obtain a Bearer Token for the connection creation window for the Jamf Pro Classic API connector.

Applies To
  • Okta Workflows
  • Jamf Pro Classic API connector
Cause

Changes to the supported authentication mechanisms for the Classic API.

Solution

The new Bearer Token authentication process is based on the previous Basic authentication process and requires no actions from users.

The connection creation window for the Jamf Pro Classic API connector remains the same.

Recommended content

Loading
Okta Workflows - February 2024 - Jamf Pro Classic API Connector Migration Guide