Deploy to Macs with MDM
On managed Macs, a configuration profile approves everything up front, so people install Periscopes without seeing any prompts.
The configuration profile
Section titled “The configuration profile”Download Periscopes.mobileconfig and push it from your MDM (Mosyle, Jamf, Kandji or any other) together with the app. It does three things:
- Pre-approves the network extension, so there’s no prompt in System Settings.
- Keeps the extension from being turned off or removed in System Settings or the Finder. Periscopes can still replace it with a newer version when it updates.
- Installs the Periscopes entry in VPN & Filters as a transparent proxy that connects on demand. It’s pinned to Periscopes’ Developer ID signature, and users can’t delete it.
Deploying the app
Section titled “Deploying the app”Deploy Periscopes with your MDM’s app deployment, using the notarized Periscopes.dmg. It has to end up in /Applications, because macOS only activates system extensions from apps installed there.
Identifiers
Section titled “Identifiers”If you build your own profile, these are the values Periscopes uses:
| Setting | Value |
|---|---|
| Team ID | M8MT9B2H7D |
| App bundle ID | io.riptides.workstation |
| Network extension bundle ID | io.riptides.workstation.network-extension |
| Extension type | Network extension, transparent proxy (app-proxy) |