PacketFence SentinelOne Quick Install Guide 3
PacketFence SentinelOne Quick Install Guide 3
The fonts used in this guide are licensed under the SIL Open Font License, Version 1.1. This license is available with a FAQ at: http://
scripts.sil.org/OFL
This guide has been created in order to help sales engineers, product managers, or network
specialists demonstrate the PacketFence capabilities on-site with an existing or potential customer.
It can also provide guidelines to setup a proof of concept for a potential PacketFence deployment
using SentinelOne to provide information about device compliance before and during network
access.
Assumptions
Quick installation
Note
All files in /usr/local/pf/html/common/ are accessible to users that are on the captive
portal. Make sure you put the agents file there or in another user-accessible location.
Where:
▪ Port should be left to default unless your SentinelOne management console is on another port.
▪ API username is the username of the user you created above in SentinelOne.
▪ Windows agent download URI is the URI on which the users should download the Windows agent.
If you followed the path in this guide, it should be /common/SentinelOne.exe.
▪ Mac OSX agent download URI is the URI on which the users should download the Mapf::errorc
OSX agent. If you followed the path in this guide, it should be /common/SentinelOne.pkg.
Note
Make sure you have passthroughs enabled before proceeding further. Instructions
on how to enable passthroughs can be found in the Passthroughs section of the
Administration Guide.
Once you have completed the configuration, you need to restart pfdns in order for the SentinelOne
specific passthroughs to be taken into consideration.
Step 4: Test
You can now test that the installation of the SentinelOne client is mandatory after the device
registration. Connect a device to your test network and register like you normally would. At the end
of the registration process you will be presented a page asking you to install the SentinelOne client
on your device. After you install the client click continue. If your access is enabled then this means
the connectivity between PacketFence and SentinelOne is good.
PacketFence polls SentinelOne at a regular interval (30 seconds by default) to find devices that have
uninstalled their agent. When it detects them as uninstalled, it automatically brings the device back
to the portal so the agent is installed.
Everytime your device connects to PacketFence using RADIUS, it schedules a provisioning check
to occur 2 minutes after the connection (controlled via violation 1300002). If the agent is inactive
on the device or was uninstalled, PacketFence will bring the device back to the portal so the agent
is installed again or brought back to an active state.