Hello, Rens. I'm facing the same behavior and have a note about this configuration every time I must update the appliance.
[Pinheiro Neto Advogados]<https://www.pinheironeto.com.br/> Robson dos Santos Hidalgo Tecnologia da Informação Rua Fernão Dias, 210, Pinheiros 05427-000 - São Paulo - Brasil tel.: (55 11) 3092 7369 [email protected]<mailto:[email protected]> www.pinheironeto.com.br De: Rens van Til via PacketFence-users <[email protected]> Enviada em: terça-feira, 15 de setembro de 2026 06:03 Para: [email protected] Cc: Rens van Til <[email protected]> Assunto: [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 ________________________________ Esta mensagem, incluindo seus anexos, pode conter informação confidencial ou privilegiada. É estritamente proibido compartilhar qualquer parte desta mensagem com terceiros, sem o consentimento por escrito do remetente. Se você a recebeu por engano, por favor, avise imediatamente ao remetente, respondendo o e-mail e em seguida apague-a. Pinheiro Neto Advogados. Todos os direitos reservados. Para mais informações, acesse: www.pinheironeto.com.br
_______________________________________________ PacketFence-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/packetfence-users
