Deploy Okta Verify to Linux devices

Use your Mobile Device Management software to deploy Okta Verify to Linux devices.

About this task

The Okta Verify for Linux app is only available as a download through the Okta Admin Console.

Unlike Okta Verify for Windows, Okta Verify for Linux has no registry or command-line installation flags. Instead, on Linux, you deploy a single JSON policy file that works with the Okta Verify client app.

Before you begin

If you want to deploy the adminconfig.json policy file before installing the package, create the /etc/okta directory, with the owner, group, and mode set to root:root 0755. The package's post-install script resets these directory settings to root:okta-ff 1775 and normalizes any existing policy file to root:root 0444.
If you want to deploy the adminconfig.json policy file after installing the package, the package installation creates the /etc/okta directory with the correct ownership.

Note:
If you deploy the adminconfig.json file after the package installation, the file retains the ownership and mode provided by your MDM solution. As the installer doesn't have an existing adminconfig.json file to check, it can't confirm if the file ownership is too restrictive.

When the Okta Verify app runs, it can't read the config file and your policy settings are ignored. To avoid this issue, explicitly set the file ownership to root:root 0444 in your MDM solution.

Procedure

Download the Okta Verify for Linux setup file through the Okta Admin Console.
Copy the Okta Verify file to your MDM server.
Deploy the okta-verify package to the device using your MDM solution, for example, Microsoft Intune, Ansible, Puppet, Chef, or a script that runs as the root user.
If you didn't deploy the /etc/okta/adminconfig.json before the package installation, deploy your device policy file.
See Okta Verify configuration settings for Linux for the supported settings.
Confirm that the adminconfig.json owner, group, and mode are set to root:root 0444, regardless of whether you deployed it before or after the package installation.
See File permissions.

What to do next

You can reboot the device to guarantee all changes are picked up.