This document details how to install OneLogin Desktop for Macs. This doc is intended for Admins.
The latest version is compatible with macOS Big Sur.
The end-user installation guide is found here: Install OneLogin Desktop for Mac (End-User Version).
Mac OS X 10.14.4 or newer (Mojave), 10.15.0 or newer (Catalina), or 11.0 or newer (Big Sur) with Swift 5 Runtime Support installed. We don't support MacOS Monterey at this time.
Your Mac must have at least one admin account that is not running OneLogin Desktop.
Macs can't join an Active Directory domain.
If you enable OneLogin Desktop for an existing account on your Mac, that account can't be signed into iCloud during installation. If you want to enable OneLogin Desktop for an account that uses iCloud keychain, exit the installer and disable iCloud keychain before rerunning the installer.
Browsers: Chrome or Safari are required to use either the PKI certificate or the OneLogin Desktop certificate to provide access to the OneLogin portal or SSO-enabled apps without having to reauthenticate.
Note: OneLogin Desktop doesn't support MacOS Monterey at this time.
OneLogin Desktop for Macs can be installed using the Silent Installer, or manually installed with the PKG installer from the OneLogin Desktop admin page or user profile page.
To install OneLogin Desktop using the Silent Install Flow, follow the steps below.
Open a terminal window and enter the following commands to write your org-specific settings, noting that versions post-3.0.63 do not require the second command:
sudo defaults write /Library/Preferences/com.onelogin.OneLoginDesktop subdomain
sudo defaults write /Library/Preferences/com.onelogin.OneLoginDesktop variation
basic | pro
Open a Terminal window on the target device.
Enter the following command to install OneLogin Desktop:
-sudo installer -pkg pathtopkg -target /
Using an MDM, install the package using the preferred method, depending on the MDM provider.
End users must use their OneLogin credentials to sign in to the Tray Application to complete the installation and binding process. Click here to access the End User guide.Note: the username attribute in the OneLogin cloud directory is required and cannot be blank.
It's safest to uninstall your old version of OneLogin Desktop prior to updating to a new version, but doing so is not strictly necessary.
To uninstall OneLogin Desktop, run
sudo sh /Library/Application\ Support/OneLogin/uninstall
Follow the steps below to install OneLogin Desktop from the profile page. Note: as of December 2020, both the Mac and Windows download links and the OneLogin Desktop/OneLogin Desktop Pro links have been split up.
On a user profile page, click the Download link in the OneLogin Desktop for Mac section.
In the downloads file, open the installer file.
A dialog launches to inform you that the package will verify if the software can be installed. Click Continue.
The Desktop installer launches. On the Introduction step, click Continue.
For the License step, you can print or save the Terms of Service.
Click Continue. On the following dialog, you have the option to read the license, Agree or Disagree. Click Agree to proceed.
For Subdomain, enter the subdomain for your org and Continue.
Select OneLogin Desktop or OneLogin Desktop Pro.
When you select an option, a dialog appears that explains the benefits of the option.
Click Close, then Continue to proceed.
Select Destination & Continue.
On the Installation Type screen, you can Change Install Location. Click Install.
Once installation is complete, a confirmation screen displays and prompts you to log in. If a notification display, open the app that was loaded onto your tray.
Once Desktop loads, pictured below, you're prompted to sign in to the Tray App.
Desktop is ready for use. In versions 3.0.65 and beyond, the following logs are available:
To download a ZIP file of your available logs for diagnostic purposes, open Terminal and type
sudo /usr/local/bin/oldesktop diagnostics.
Note: OneLogin does not recommend configuring a uniform Apply MFA policy for OneLogin Desktop 3.0.65+ if there are Windows users on the same policy. If your organization fits that case, configure a separate policy for Windows and Mac users or remain on release 3.0.63.