Fixed an issue that incorrectly allowed TCP port scanning via LDAP directory service settings in Jamf Pro. Fixed an issue that prevented disabling User Login for Self Service for macOS if it was enabled prior to upgrading to Jamf Pro 10.25.1. Fixed an issue that caused the Jamf Pro API to fail to rename an Apple TV device. Computers attempting to enroll with Jamf Pro via a PreStage enrollment with an expired certificate signed by “Apple iPhone Device CA” no longer fail to enroll or display a 403 error message. Fixed an issue that allowed certain Self Service API endpoints to incorrectly provide limited information without authentication. The Jamf Pro API Swagger documentation no longer allows HTML injection. Fixed an issue that caused the Send Update button in the Conditional Access settings to send incorrect password values to Microsoft Azure, resulting in a loss of compliance for all computers. Fixed an issue that sometimes prevented an updated in-house app from updating on a device if the app had not finished uploading in Jamf Pro. Fixed an issue that caused Jamf Pro as SCEP Proxy and the Jamf ADCS Connector to incorrectly treat pending responses as failed when deploying configuration profiles. Fixed an issue that, in some instances, prevented the site assigned to an object from being changed. Fixed an issue that caused User Enrollment to fail when a third-party signing certificate was added to the User-Initiated Enrollment settings. Fixed an issue that caused Jamf Pro to incorrectly display settings in the Applications & Custom payload of a computer configuration profile. Fixed an issue that caused User-Initiated Enrollment LDAP Access Group names to display incorrectly if multiple groups were mapped to the same GroupID. Fixed an issue that prevented users from enrolling via user-initiated enrollment and administrators from viewing the User-Initiated Enrollment settings if users were assigned to an access group where the group ID was mapped to an attribute with a non-integer value and the LDAP group name was listed alphanumerically before the "All LDAP Users" group. Fixed an issue that caused Jamf Pro to fail to distribute a later version of a B2B app. Fixed an issue that caused Jamf Pro to become unresponsive if an invalid activation code was entered twice. Fixed an issue in which certain credentials used by the Jamf Pro web application were hard-coded. Fixed an issue that caused Jamf Pro servers hosted on Windows to be unable to send email reports from advanced searches for computers and mobile devices. This will prevent issues with mass deletion of users with device assignments. Added additional safeguards to prevent the creation of duplicate users. Uploading a new signing certificate for the external CA when it was already enabled for enrollment or for configuration profilesĭisabling the use of the external CA for enrollment This condition could last up to six hours and could be triggered by the following events:Įnabling the use of the external CA for enrollment when it was already enabled for configuration profilesĮnabling the use of the external CA for configuration profiles when it was already enabled for enrollment Fixed an issue that caused members of a clustered Jamf Pro environment to not synchronize with the signing certificates needed for issuing device identity certificates or signing profiles. Fixed an issue that, when viewing from a site, caused attachment downloads in inventory records to fail to download or be unable to be opened after downloading. framework files when uninstalling an indexed package with a policy. Fixed an issue that prevented deleting folders with symlinks or.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |