Comment on page
To download the macOS installation package log in to the dope.console. From the top right-hand corner select the download button
. This will provide the different dope.endpoint installation packages available for download.
In the case of macOS, the dope.endpoint has one universal installation package that supports:
• Apple Intel • Apple Silicon (Native)
After selecting the installation package you require, a ZIP file will be downloaded to your device. The ZIP file will be called dope_security_mac_<processor type>_<build number>.zip
Extract the ZIP file, it will contain the following three files:
- dope.security-<build number>.pkg — The dope.endpoint installer.
- dope.security.crt — The dope.security Root CA, required for SSL inspection.
- agent_parameters.json — Tenant-specific data required for the installation process.
All three files must be in the same directory or the installation will FAIL.
To install the dope.endpoint, double click on the PKG file. This will launch the Installer UI.
From here select Continue. A new screen will appear:
There will be a prompt to allow the dope.security Root CA to be installed:
The final prompt is to allow the dope.security application to run. There's a prompt to open the macOS security and preferences settings:
Open the security preferences dialog box. Run the dope.security application:
Once these steps are complete a dope.security icon can be seen in the macOS menu bar
When the dope.endpoint has been successfully installed, and endpoint authentication has been enabled (see: Users), one of these dialogs will be displayed prompting you to login via either your Google or Microsoft O365 corporate email.
SSO Prompts for Google and Microsoft O365
Log in with the appropriate corporate email address.
If enabled, Multi Factor Authentication (MFA) will be required.
Once the user has successfully authenticated, the dope.endpoint will be configured with the dope policy you have assigned them in the dope.console. If you have not assigned them a specific policy, they will automatically be assigned the Base Policy.
To check that the authentication was successful, simply click on the
icon in the menu bar. This will show the following information including the logged-in user.