Jamf Trust Configuration Changes for iOS 15.6 and Later
Disclaimer:
This article is no longer being updated.
As of iOS 15.6, Apple introduced changes to how iOS and iPadOS handle Per-App VPN and Proxy traffic. Jamf Trust and Wandera utilize Apple Per-App VPN triggers for Cloud Proxy configurations, enabling devices to report their statuses and send device data to Jamf Security Cloud.
Most customers do not need to take any action—Jamf added custom routing rules for the default domains included in the Jamf Trust and Wandera (legacy) apps.
However, if you modified your configuration profile to include additional Safari domains to trigger the Per-App VPN, you need to take the following steps to ensure network connectivity isn't interrupted for your users:
Checking the Safari domains in your configuration profile
Entering new rules in RADAR, if required
Step 1: Checking the Safari Domains in Your Configuration Profile
If your Safari domains list only contains the default domains above, no further action is required.
If there are any other domains in the Safari domains list, proceed to step 2.
Step 2: Entering New Rules in RADAR
If there are any non-default domains in your Safari domains list, you must add rules in RADAR to bypass these domains and ensure uninterrupted service.