LogoLogo
  • Introducing dope.swg
    • Changing the Rules...
    • Quick Start Guide
      • Create a dope.swg Account
      • Get Started with the dope.endpoint
      • Import User and Group Data
      • Create a dope.swg Web Policy
    • Mitre ATT&CK and Nist CSF
  • dope.console
    • Analytics
      • Overview dashboard
      • Policy View
      • Productivity
      • Shadow IT
      • Detail View
    • dope.swg Policy
      • Editing the Base Policy
      • Adding Policy Exceptions
      • Assigning a Block Page
      • Creating Custom Categories
      • URL Bypass List
      • Application Bypass List
      • Default Bypass List
      • Cloud Application Control (CAC)
        • Microsoft O365
        • Google
        • Box
        • Salesforce
        • Dropbox
        • Slack
        • WebEx
      • Custom Policy
      • Policy Assignment
      • Policy Inheritance and Customization
    • CASB Neural
      • Microsoft 365 - Authentication
      • Google - Authentication
      • CASB DLP
        • DLP Files Table
    • Endpoint Manager View
      • Searching the View
      • Filtering and Sorting the Endpoint View
      • Endpoint Count
      • Running Diagnostics
      • Disable Endpoint
    • Settings
      • General
      • Block Pages
      • Endpoints
      • Users
        • Importing from Google
        • Why not SAML & SCIM?
      • Audit Log
      • SIEM Integration
        • Category & Verdict Mappings
      • API Client Credentials
      • Billing Details
    • Notifications
      • SSL Errors
  • dope.endpoint
    • Trusted Process Names
    • Generate Diagnostics
    • Disable Endpoint
    • Installing using MDM on Mac
      • Using JAMF
      • Using Kandji
      • Using Intune
    • Installing using Intune on Win
    • Mac Installer
      • Installation Process - Silent
      • Uninstall
      • Endpoint Authentication
    • Windows Installer
      • Installation Process - Silent
      • Uninstall
      • Endpoint Authentication
    • dope.endpoint UI
      • Windows UI
      • macOS UI
    • Automatic Updates
  • Release Notes
  • DOPE.APIs
    • Public API Specification
Powered by GitBook
On this page
  • Downloading the macOS Installation Package
  • Select the installer package for your device
  1. dope.endpoint
  2. Mac Installer

Installation Process - Silent

PreviousMac InstallerNextUninstall

Last updated 11 months ago

Downloading the macOS Installation Package

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)

This page is for a device where a Mobile Device Management (MDM) profile has not been installed. To install on a device with an MDM profile installed see Installing using MDM on Mac

Select the installer package for your device

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

The ZIP file 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 go to a terminal and enter the following command: 

sudo installer -pkg dope.security-<build number>-<process type>.pkg -target /

Running this command will kick off the installation process but with no UI. There will be a prompt to allow the installation to start:

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:

All of the prompts above will not appear on a device where a MDM profile has been installed. For more details see Installing using MDM on Mac.

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.

Log in with the appropriate corporate email address.

Multi Factor Authentication (MFA) will also be required if enabled

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.

Where endpoint authentication has not been enabled (see: Users) the user will not be prompted to authenticate and will get the Base Policy.

Once these steps are complete a dope.security icon can be seen in the macOS menu bar .

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.

Google Login Example