MFA for PacketFence
PacketFence is the open-source network access control (NAC) system from Inverse. It runs its own RADIUS service and decides who gets onto the network and with what role. PacketFence can send password checks to an external RADIUS server as an authentication source, but it has no second factor of its own. Authnull becomes that source and requires MFA before PacketFence accepts the login. Your connection profiles, roles and enforcement stay as they are.
PacketFence forwards the login; Authnull adds the factor.
PacketFence sends the login to Authnull as a RADIUS authentication source. Authnull checks the password against your directory, asks for the factor, and returns Access-Accept. PacketFence then applies its own role and enforcement rules.
Configure MFA for PacketFence
Real steps — the exact menus, fields, and values. Follow along in your console; the whole thing takes about 25 minutes.
Add Authnull as a RADIUS source
Create a new internal authentication source of type RADIUS with the Authnull connector IP, port 1812, the shared secret and a 60-second timeout.
Add role rules
In the source, add rules that give users approved by Authnull the right PacketFence role and access duration.
Use it in a connection profile
Add the Authnull source to the connection profile that handles your portal logins, above any other sources.
Test the login
Sign in through the PacketFence portal with a test account, approve the factor, and confirm the login in the PacketFence audit log and the Authnull logs.
Closes the MFA gap auditors look for
Enforcing MFA on PacketFence gives you evidence for the remote-access and privileged-access controls in SOC 2 and the access requirements under CCPA — with per-login logs you can hand straight to an assessor.
Add MFA to PacketFence — free to start.
Spin up Authnull, point PacketFence at it, and enforce a factor on a pilot group today. No card, no rip-and-replace.