Releases: jamf/Jamf-Switcher
Jamf Switcher
Jamf Switcher
Jamf Switcher
- #18 - Added support for the new failover URL format introduced in Jamf Pro 10.45.0
What's Changed
Full Changelog: 1.4.1-beta1...1.5-beta1
Jamf Switcher
Jamf Switcher
Changes in this release:
- Removed the LetsMove framework (to stop the SystemPolicyAppBundle protection being triggered on macOS 13.0+)
- Updated Sparkle to Sparkle 2
- Resized the app icon
- Added support for bearer token auth
- Before flushing will check to see if a policy is disabled, and only flush if enabled. And will notify if disabled in searches.
- Stopped the window from being closed.
Full Changelog: 1.3.1...1.4
Jamf Switcher
#11 Resolves an issue where Jamf Switcher shows no data due to the XML with Jamf 10.33.0 changing <attribute name="jssdescription" type="string">JSS</attribute>
to: <attribute name="serverdescription" type="string">JSS</attribute>
. With this release we should work with both.
Jamf Switcher
Changes in this release:
- Removed the LetsMove framework (to stop the SystemPolicyAppBundle protection being triggered on macOS 13.0+)
- Updated Sparkle to Sparkle 2
- Resized the app icon
- Added support for bearer token auth
- Before flushing will check to see if a policy is disabled, and only flush if enabled. And will notify if disabled in searches.
- Stopped the window from being closed.
Jamf Switcher
#9 - Adds support for Jamf Pro 10.30+'s new Self Service bookmark format.
Jamf Switcher
Addresses:
#3 - Silicon support, from updating LetsMove.framework to 1.25 and Sparkle.framework to 1.24.0
Jamf Switcher
Addresses the following:
#4 - Adds "Find Policy" functionality via CMD + F or Window > Find Policy.
#5 - Adds "Flush Policy" functionality via OPTION+ CMD + F or Window > Flush Policy.
#6 - Adds "Export" functional via CMD + E or Window > Export.
#7 - Adds full screen support.
#8 - Tested on Big Sur with amendments made as needed.
For #4, #5, and #6 these work across any Jamf Pro listed in the main view. So if searching for a sub section then they will be enacted upon our their details will be exported, alone.
#4 and the #5 happen via the Jamf Pro API, as such you'll be asked for details which will be stored in your keychain for when those options are ran again.