Hello Andrew,
just remove it from the file and it will be ok.
Regards
Fabrice
Le 20-06-24 à 11 h 01, Lierman, Andrew via PacketFence-users a écrit :
I keep getting messages about invalid parameter device_registration
for profiles.
What do I need to change to fix this issue? Is there a
Hi,
I think I found the problem.
Update process (10.0.1 to 10.1) creates the file:
/usr/local/pf/conf/radiusd/eap_profiles.conf
This file is initially empty
After performing step 18.2 of the update guide :
/usr/local/pf/addons/upgrade/to-10.1-move-radius-configuration-parmeters.pl
In the file :
i am running the latest version of PacketFence, Unifi 5.12 and FortiOS 6.0.4.
I have a single SSID configured with MAC Auth and external captive portal
pointing to packetfence.
When a device connects to the SSID for the first time, it is redirected to the
pf captive portal where they can auth
You need to contact google and request that your oauth client be
whitelisted for wifi login.
On Mon, Jun 29, 2020 at 9:44 AM Akram Abdallah via PacketFence-users
wrote:
>
> Hello ,
>
> When trying to use the Google Auth in Packetfence portal i get this message
> 403 : disallowed_useragent"
Hi Guys,
I am trying to get machine authentication working so that if a machine is a
member of the Active Directory Domain Computers group it will join wifi without
prompting the user for anything.
The access points are all Meraki.
On packetfence I have the following:Connection Profile