Deploy Aikido Device Protection with Rippling
Use Rippling to deploy Aikido Device Protection across your managed macOS fleet with the required permissions in place.
All devices must be enrolled in Rippling MDM before you begin.
Installation
What you'll need
Before starting, make sure you have the following from the Aikido Device Protection dashboard:
Your Device Protection Token (copied from the user group selector)
The Shared Root CA Certificate (
.pemfile — downloaded in the dashboard)The Aikido Device Protection installer (
.pkgfile — downloaded in the dashboard)
If you're missing any of these, go back to the Aikido Device Protection dashboard, click Connect Device, and complete the pre-flight steps.
Upload the Aikido Device Protection configuration profile
In Rippling, go to IT → Device Management → Configurations and select the macOS tab.
Click Upload.
Enter a Policy name (e.g. "Aikido Device Protection").
Set Platform to macOS.
Drop or select the downloaded
.mobileconfigfile.Click Save & continue.
Rippling requires .mobileconfig uploads to be done from a Mac. Uploading from another operating system may silently fail.
This profile allows the Aikido Device Protection system extension to load silently, enables the network content filter, and stops users from disabling background services in System Settings → Login Items.
Deploy the configuration profile
In Configurations, switch to the Everything Else tab.
Find the profile you just created.
Click the three-dot menu on the right and select Deploy.
Select the target employees or devices and click Save.
Deploy the Aikido Device Protection CA certificate
In Rippling, go to IT → Device Management → Configurations and select the macOS tab.
Click Upload, set Platform to macOS, and upload the Shared Root CA Certificate (
.pemfile).Click Save & continue.
In Configurations, find the certificate you just uploaded, click the three-dot menu, select Deploy, and assign it to the same target employees or devices.
Verify the certificate appears on a test device before deploying the agent package.
Upload the Aikido Device Protection installer
In Rippling, go to IT → Software.
Click Upload Software.
Fill in the following fields:
Name: Aikido Device Protection
Operating System: macOS
Description: Aikido Device Protection
Under Upload Installer File, drop or select the Aikido Device Protection
.pkgfile.Under Pre-install script, paste the script below. Replace
AIK_SAFE_CHAIN_TOKENwith your real token.
#!/bin/zsh
echo "AIK_SAFE_CHAIN_TOKEN" > /tmp/aikido_endpoint_token.txtClick Submit.
Click Add on the newly created software item, then click Finished Selecting.
Deploy in the right order
Order matters. Both the configuration profile and the CA certificate must reach the device before the pkg. If the pkg installs first, macOS can ask the user for extra permissions.
Confirm the Aikido Device Protection configuration profile is installed on a test device.
Confirm the Aikido Device Protection CA certificate is installed on a test device.
Find the Aikido Device Protection software item under IT → Software, click Edit, select the target employees or devices, and click Save.
Newly created software items in Rippling may stay in a "Pending" status for a few minutes before they can be deployed.
Reboot devices after installation
In Rippling, go to IT → Devices.
Select the target devices and choose Restart from the bulk actions menu (or open an individual device and select Restart from device actions).
The agent fully activates on the next boot.
Verify the deployment
On a test device, confirm:
The system extension is activated:
systemextensionsctl list | grep aikidoExpect to see the extension marked
[activated enabled].Open System Settings → General → Login Items & Extensions and confirm the Aikido Device Protection entries cannot be toggled off.
Troubleshooting
Users still see the popup
Make sure the configuration profile is scoped correctly and installed before the package policy runs
Extension is waiting for user approval
Check the System Extensions payload and confirm the team ID and bundle ID match exactly
The package installs but the device does not connect
Confirm the token script ran before the package install and that the token was copied correctly
Duplicate extension entries appear
Reboot the device
The content filter is not approved silently
Re-upload the .mobileconfig profile and verify it is installed on the device
Last updated
Was this helpful?