Installing the Access Manager Agent on macOS
Last updated
Was this helpful?
Last updated
Was this helpful?
The agent must be able to validate the AMS server certificate. If you are using a self-signed certificate, or a certificate issued from a private CA, you'll need to to the system keychain, and .
The agent itself runs using launchd, and as it requires access to reset the root password, must be run as the root user.
The agent requires macOS 12 or later. Packages are available for both Intel and M-series Macs.
Download the agent for the appropriate architecture from the downloads page, or directly from the package repository using the script below.
Ensure the package is valid, and has been signed by Lithnet Pty Ltd (5DK86QQXK3)
You can open the package from finder, or use the installer command line tool to install the package
Once the package is installed, it must be configured to talk to your AMS server. You can run the following command to perform an interactive installation
If your device is joined to an Active Directory domain, you can use Windows authentication (kerberos) to authenticate to the AMS server. Otherwise, you will need to create a registration key on the AMS server and use that instead.
To perform a non-interactive installation, use the following command, replacing the server name, and registration key as appropriate. You can generate new registration keys using the AMS configuration tool.
Install the agent using a registration key
Install the agent using Windows authentication (kerberos)
Check the log using the instructions in the Viewing the log files section below to ensure the agent registered correctly.
On the Access Manager server, go to the Access Manager Agent/Devices page, and ensure that the devices you installed the agent on have appeared in the device list. If you configured your registration key to require manual approval, you must approve the devices before they can be accessed.
The Lithnet Access Manager Agent runs as a daemon using launchd. You can use standard launchd commands to start, stop and restart the agent.
You can use the uninstallation script provided to remove the agent from the computer.
The agent logs can be viewed using the Console app, or using the command line
To show all events in the log use the following command
To show a live stream of log messages use the following command
The agent creates and uses the following files and folders.
/Library/Application Support/Lithnet/AccessManagerAgent/Configuration/LithnetAccessManagerAgent.conf - The main configuration file for the application. This contains the AMS server name and other settings relevant to the application.
/Library/Application Support/Lithnet/AccessManagerAgent/Configuration/LithnetAccessManagerAgent.state - This contains information used by the agent to store its current state information. This file should not be modified. It is generated by the app when it is run, and is not part of the installation package.
/Library/Application Support/Lithnet/AccessManagerAgent/Core - This directory contains the application binary files.
/Library/Logs/Lithnet/AccessManagerAgent/ - This directory contains the agent log files.
/Library/LaunchDaemons/io.lithnet.accessmanager.agent.plist - The launchd entry for the agent, symlinked from the application directory.
If the hostname provided does not match exactly the External host name value configured on the , the agent will fail to connect to the server