Giters

univ-of-utah-marriott-library-apple / jctl

`jctl` uses `python-jamf` to select objects to create, delete, print and update. It allows performing Jamf Pro repetitive tasks quickly and provides options not available in the web GUI. It is similar to SQL statements, but far less complex.

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Add Bearer Token Authentication

uurazzle opened this issue · comments

commented

Hi:

Please add support to add bearer token authentication and provide backward compatibility with if use of Basic authentication is required (v10.34.0 and earlier).

Beginning in version 10.35.0 of Jamf Pro (scheduled for release in early January), the Classic API will now support Bearer Token authentication. This is the same authentication mechanism used by the Jamf Pro API, which brings further feature parity between our APIs as well as an added layer of security.

The 10.35.0 release of Jamf Pro will also include the deprecation of basic authentication via the Classic API which will be removed at a future time (estimated removal date: August-December 2022). Customers will have the ability to disable basic authentication before support is fully removed and we anticipate security conscientious customers will be eager to adopt these changes.

Jamf recommends providing backwards compatibility for your applications that interface with the Classic API. By implementing a version check of Jamf Pro, your application can determine whether Bearer Token authentication is supported (v10.35.0 or later) or if use of Basic authentication is required (v10.34.0 and earlier). The jamf-pro-version endpoint within the Jamf Pro API returns the version of the Jamf Pro Server, to help your application determine authentication compatibility with a given Jamf Pro Server. Jamf recommends including a preference to allow users to select the authentication schema based on their environment configuration or dynamically determining which authentication mechanism to use based on the Jamf Pro Server version.

Attempting to interact with a Jamf Pro environment that has disabled support for Basic authentication will result in a 401 Unauthorized response. It is also worth noting that this response is no different than the response received when using invalid credentials to interact with the Classic API via Basic authentication.

All existing integrations that leverage Jamf Pro’s Classic API will require an update to support bearer token authentication. More details regarding specific timelines will be communicated as they become available, but please plan for these changes to occur in 2022.

See the following Jamf web site for details:
https://developer.jamf.com/jamf-pro/docs/classic-api-authentication-changes

commented

This really is a python-jamf feature than a jctl and the issue has been added to jctl and this ticket will be closed.