Classification: PUBLIC Hi Rens
I had the same issue when I was configuring PacketFence. The issue is that FreeRADIUS can't authenticate users with spaces. We are renaming all our machines to not have spaces. We are assigning machines to a group dynamically, with a filter not to capture machines with spaces in the names. Thanks Kobby Kobby Gamzo Group Head of IT and InfoSec W: www.msqpartners.com MSQ is a certified B Corp company. ________________________________ From: Rens van Til via PacketFence-users <[email protected]> Sent: 15 September 2026 10:02 To: [email protected] <[email protected]> Cc: Rens van Til <[email protected]> Subject: [PacketFence-users] Best practice for allowing spaces in RADIUS User-Name Hi everyone, We are running into an issue with 802.1X authentication for macOS devices that are Microsoft Intune-joined and validated against Entra ID. The certificates generated for these macOS devices include spaces in the Subject / Principal Name field (e.g. User-Name contains spaces). By default, PacketFence rejects these authentication requests due to the following check in /usr/local/pf/raddb/policy.d/filter: Codefragment if (&User-Name =~ / /) { update request { &Module-Failure-Message += 'Rejected: User-Name contains whitespace' } reject } We have tried a few approaches to resolve this permanently: 1. Modifying /usr/local/pf/raddb/policy.d/filter directly: Commenting out the if (&User-Name =~ / /) block works, but this file gets overwritten during PacketFence upgrades. 1. Disabling filter_username in /usr/local/pf/raddb/sites-enabled/packetfence: Commenting out the filter_username call in the authorize section is persistent across reloads, but this disables the entire username filtering policy altogether, which is broader than we'd like. Question: What is the recommended / persistent way in PacketFence (v15) to allow spaces in RADIUS User-Name attributes without completely bypassing filter_username or having local policy edits overwritten by maintenance updates? Is there a supported template override mechanism or a configuration setting we should be using? Thanks in advance for any insights! Best regards, Rens MSQ Partners Ltd or any of its subsidiary companies may not be held responsible for the content of this email as it may reflect the personal view of the sender and not that of the company. Should you receive this email in error, please notify the sender immediately and do not disclose, copy or distribute it. While MSQ Partners Ltd scans all outbound emails for viruses, it cannot be held responsible for any infected files that you may receive. MSQ Partners Ltd advises all recipients to virus scan any file attachments. MSQ Partners Ltd | Registered in England No.: 7745643 | Registered Office: 34 Bow Street, London, WC2E 7AU
_______________________________________________ PacketFence-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/packetfence-users
