![]() ![]() Creates a local xml file to store smart group data.Downloads all patch titles from all sources on your Jamf Pro server and saves them to a local file.The script performs the following actions: Once configured the script should be able to update a single smart group with many app versions so that you can identify all computers with one or more apps that are out of date. Optionally enter any recipes from your recipe list that should be excluded.Enter the ID and name of the group that you would like to update.Enter the user account you are running AutoPkg from.Read access to Jamf Pro Server Settings > Internal Patch SourcesĬonfiguring the script requires the following:.Read access to Jamf Pro Server Objects > External Patch Sources.The Jamf Pro API user that is configured for AutoPkg will need two additional permissions: I used homebrew to accomplish this with: brew install jq The next prerequisite is to install jq so that we can easily parse JSON data. If that is not true in your environment, you can add something like the following to each recipe override:Īfter adding the processor, running the recipe again should generate the latest_version.json file in your AutoPkg cache. This means that all of our recipes already include the PATCH_SOFTWARE_TITLE_ID key. In our environment we have recipes configured to upload new packages to Jamf Pro, then add those new updates to patch management policies. This script assumes that you are using AutoPkg with Graham Pugh’s Jamf Upload processors. To make this work there is bit of setup involved. So I created a workflow to automate updating that smart group. My only issue with implementing Thom’s workflow is that when using AutoPkg (and Jamf Upload), updating the smart group that identities out of date apps can become cumbersome rather quickly. Thom goes into some detail in that post about why this might be needed/preferred vs using the built-in notifications. In it, Thom discusses using a custom alert that directs users to the “Notifications” section of Self Service where they can apply pending updates. I was inspired by the Jamf Tech Thoughts post, “ Custom Self Service Patch Notifications” by ThomM. Additional data will be required either in the form of a parameter value and/or a request body.This post will outline a method to get app versions from AutoPkg and apply those version numbers to a single smart group in Jamf Pro. Getting StartedĪfter the collection has been imported and valid values have been defined for the variables, all calls should be supported with minimal input required. For more information on authentication changes to the Classic API, see the Jamf Developer Portal. Tokens will be requested as necessary, so no interaction with authentication endpoint should be necessary. This version of the collection utilizes scripts to manage the Bearer Token, which is a new authentication method supported in version 10.35.0 and later of Jamf Pro. Protocol, hostname and port of the Jamf Pro environment Password of the user authenticating to Jamf Pro Username to authenticate to Jamf Pro with Hostname and port of the Jamf Pro environment Follow Postman's documentation to Manage Environments. Using variables at the collection level is not currently supported by the script that performs that authorization token requests. This collection utilizes the following variables which should be defined within the environment variables. Download the JSON included in this repo and select the.For Jamf Pro Version 10.35.0 and later: Click the button to automatically import the collection into your Postman app.For Jamf Pro version 10.34.0 and earlier: Click the button to automatically import the collection into your Postman app.Use the following options to import the collection into Postman: All query parameters that have a defined list of acceptable values denote the allowed values in the description of the parameter.computercommmands and mobiledevicecommands). ![]() Endpoints that have conditional inputs in the form of parameters or request bodies should include multiple examples (e.g.All GET operations include at least one example response.Pull requests or issue submissions are encouraged to enhance or update this data.This request body may not include all fields supported by the body of the given object, however it will include those required to successfully create the object.All POST operations include a pre-populated request body.The following expectations were used when designing this collection: This article describes the recommended Postman configuration and setup process to import the collection, configure variables to connect it to your Jamf Pro environment and begin testing API calls and interacting with your Jamf Pro environment via the Classic API. It provides a quick method to interact with all non-deprecated endpoints. This collection is provided to assist Jamf Pro users of the Classic API. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |