Request Time
RADIUS Request
Event-Timestamp = "Feb 6 2025 18:39:18 UTC",
FreeRADIUS-Client-IP-Address = "192.168.110.50",
Module-Failure-Message = "rest: Server returned:",
Module-Failure-Message = "rest: {"Reply-Message":"CLI or VPN Access is not
allowed by PacketFence on this
switch","control:PacketFence-Authorization-Status":"allow"}",
NAS-IP-Address = "192.168.110.50",
PacketFence-KeyBalanced = "86318e52f5ed4801abe1d13d509443de",
PacketFence-Radius-Ip = "192.168.11.206",
Realm = "null",
Stripped-User-Name = "ali",
User-Name = "ali",
User-Password = "******"
RADIUS Reply
REST-HTTP-Status-Code = "401"
On Thu, Feb 6, 2025 at 5:12 PM Ma, Zhihao <z...@akamai.com> wrote:
> Hi Mahmoud
>
> After the configuration, you’ll need to (re) start
> packetfence-ntlm-auth-api
>
> And do a machine account test (or refresh the domain lists to see if the
> joining status is green)
>
> Taking a look at packetfence logs would probably give you the exact reason
> of an authentication failure
>
>
>
> Thabks
>
>
>
> --
>
> *Zhihao Ma*
> *Software Engineer Senior*
>
> [image: signature_1115100776]
>
> *Office:* +1 613 714 6311
>
> Akamai Technologies - Inverse
> 145 Broadway
> Cambridge, MA 02142
>
> Connect with Us:
>
> [image: signature_1306080453] <https://community.akamai.com/> [image:
> signature_2052239702] <http://blogs.akamai.com/> [image:
> signature_715343381] <https://twitter.com/akamai> [image:
> signature_1033247773] <http://www.facebook.com/AkamaiTechnologies> [image:
> signature_1743836937]
> <http://www.linkedin.com/company/akamai-technologies> [image:
> signature_381820823]
> <http://www.youtube.com/user/akamaitechnologies?feature=results_main>
>
>
>
>
>
> *From: *Mahmoud Mabrouk via PacketFence-users <
> packetfence-users@lists.sourceforge.net>
> *Reply-To: *"packetfence-users@lists.sourceforge.net" <
> packetfence-users@lists.sourceforge.net>
> *Date: *Thursday, February 6, 2025 at 10:05
> *To: *"packetfence-users@lists.sourceforge.net" <
> packetfence-users@lists.sourceforge.net>
> *Cc: *Mahmoud Mabrouk <mahmoudli...@gmail.com>
> *Subject: *[PacketFence-users] Issue with 802.1X Authentication and AD
> Integration in PacketFence v1
>
>
>
> Hi everyone, I'm currently working on integrating PacketFence version 14
> with Active Directory for 802. 1X authentication based on user group
> membership. I've followed the steps in the documentation, but I'm
> encountering an issue
>
> ZjQcmQRYFpfptBannerStart
>
> *This Message Is From an External Sender *
>
> This message came from outside your organization.
>
> ZjQcmQRYFpfptBannerEnd
>
> Hi everyone,
>
>
>
> I'm currently working on integrating PacketFence version 14 with Active
> Directory for 802.1X authentication based on user group membership. I've
> followed the steps in the documentation, but I'm encountering an issue where
> users are not being authenticated correctly.
>
>
>
> Here are the details:
>
> - PacketFence version: 14
>
> - AD domain: example.com
> <https://urldefense.com/v3/__http:/example.com__;!!GjvTz_vk!Sy138QxgdETnHiB_4n0vskWatX1_hRQCR_PDqWMgJuvpy_etWuf2jkD0iyAdI9xZy-RFpaMe-Or4E2tWi-AID4pwPs2cCdU$>
>
> - Error message: "Authentication failed for user [username]"
>
>
>
> Steps I've taken so far:
>
> 1. Configured the AD domain in PacketFence.
>
> 2. Set up RADIUS authentication.
>
> 3. Configured 802.1X authentication.
>
>
>
> Any help or suggestions would be greatly appreciated!
>
>
>
> Thank you,
>
> Mahmoud
>
>
_______________________________________________
PacketFence-users mailing list
PacketFence-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/packetfence-users
