Re: [PacketFence-users] Violation 1300003 force-closed after successful Captive Portal Authentication

Hello Ricardo, i mean that: ### httpd.portal logger ### log4perl.rootLogger = TRACE, HTTPD_PORTAL and the packetfence.log Regards Fabrice Le 2017-11-28 à 17:01, Ricardo Underwood via PacketFence-users a écrit : > Hello Fabrice, > > I already had those settings in the

Re: [PacketFence-users] Violation 1300003 force-closed after successful Captive Portal Authentication

Hello Fabrice, I already had those settings in the conf/log.conf.d/httpd.portal.conf, I tried again to connect to the Wireless Network and here is the entries in the httpd.portal.access log: Nov 28 16:44:39 packetfence httpd_portal: 192.168.2.126 127.0.0.1 - - [28/Nov/2017:16:44:39 -0500]

Re: [PacketFence-users] Violation 1300003 force-closed after successful Captive Portal Authentication

Hello Ricardo, i am not seeing what is wrong but it's not suppose to have that in the log: Can't re-evaluate access because no open locationlog entry was found Can you put the portal in debug mode ? conf/log.conf.d/httpd.portal.conf: ### httpd.portal logger ### log4perl.rootLogger = INFO,

Re: [PacketFence-users] Violation 1300003 force-closed after successful Captive Portal Authentication

Hello, Is there anyone that can give me a hand, a hint or a lead on this matter, I really need to figure out what the problem is. Thanks in advance, Ricardo Underwood On Wed, Nov 22, 2017 at 2:22 PM, Ricardo Underwood wrote: > Hello, > > I've been configuring

[PacketFence-users] Violation 1300003 force-closed after successful Captive Portal Authentication

Hello, I've been configuring Packetfence to work with our wired and wireless network, at the moment I'm trying to get the Wireless working using Captive Portal, I'm using oauth2 with Google as per we want to take advantage of our Google Apps as our authentication method for company wide, we use