It's still the same in the logs.
Can you share your prifiles.conf and authentication.conf file ?
Regards
Fabrice
Le 20-02-11 à 12 h 02, Nadim El-Khoury a écrit :
Hi Fabrice,
I am sorry to report that nothing works. I am still seeing the same
behavior.
I deleted all the connection profiles
Hi,
yes, you have to.
Have a look on my Post from January.
I described there how you can check if you have insecure LDAP connections on
you domain controllers:
https://www.mail-archive.com/packetfence-users%40lists.sourceforge.net/msg18067.html
Tobias
Tobias Friede
Hi Nicolas,
Thanks, I have noted for a next time. I did a server reboot and took the
role name change.
Greetings
El mar., 11 feb. 2020 a las 14:00, Nicolas Quiniou-Briand ()
escribió:
>
>
> On 10/02/2020 19:26, Rokkhan wrote:
> > Let me know if it happens the same on your deployment to verify
Can anyone tell me if the pending changes to LDAP Microsoft announced are going
to effect packetfence.
Source:
https://portal.msrc.microsoft.com/en-us/security-guidance/advisory/ADV190023
We have out PF cluster using our AD servers as an authentication source. Will
I need to set the LDAP
Hi,
I tried to upgrade from version 9.1 to 9.3, I followed the steps in the
documentation, but after finishing the system it gets stuck in "cheking
configuration sanity...", and it doesn't go away ... now I have the system
out of service.
image in attach
Can anyone help?
Thanks
Regards
Here are the logs parts
packetfence.log
Feb 11 08:35:57 nac9-1 pfipset[30180]: t=2020-02-11T08:35:57+0100 lvl=info
msg="No Inline Network bypass ipsets reload" pid=30180
Feb 11 08:36:34 nac9-1 packetfence_httpd.aaa: httpd.aaa(30325) INFO:
[mac:10:65:30:d5:bd:9c] handling radius autz request:
Ok so assign the default realm in the authentication source and/or the
realm springfieldcollege.edu.
Le 20-02-10 à 22 h 42, Nadim El-Khoury a écrit :
Hi Fabrice,
I want to thank you for taking the time to look into the log file.
Yes, we have AD configured as an authentication source. I added
Hello Nadim,
it depend of the filter and the order.
The default one will always be the last one and after that the first
match win.
Regards
Fabrice
Le 20-02-10 à 22 h 49, Nadim El-Khoury a écrit :
Hi Fabrice,
I have another question for you.
How does PF choose which connection profile
Hello,
On 03/02/2020 21:37, Christian McDonald via PacketFence-users wrote:
So, I'm guessing authentication sources operate on a first-match
basis? Meaning, that if I had an authentication source that matched
the user but *didn't apply* an administration access level at say
priority 1, any
On 10/02/2020 19:26, Rokkhan wrote:
Let me know if it happens the same on your deployment to verify if its
just my servers or a bug.
When you make a manual edit in a conf file, you should run: `pfcmd
configreload hard` on CLI.
--
Nicolas Quiniou-Briand
n...@inverse.ca ::
Hi,
On 11/02/2020 09:17, Franck Rakotonindrainy via PacketFence-users wrote:
but when radius (AD) authentication is send to the node I call 9-1, it
never succeed
1. Did you see something interesting in packetfence.log or radius.log on
9-1 node ?
2. If you use EAP-PEAP, are you sure 9-1 is
Hi all,
I have eliminated most of the errors below in terms of reading KeyInfo from
KeyDescriptors (that was due to my SP certificates being invalid). However I am
still seeing “Unknown IO Error” in /usr/local/pf/logs/httpd.portal.error and
the following error in the captive portal on my
Hello,
I have a packetfence cluster of 3 nodes (PF9.3 running on Debian 9)
I have an issue with one member of the node in the cluster, the authentication
request are proxied to any member of the cluster (I don't understand following
which policy)
but when radius (AD) authentication is send to
13 matches
Mail list logo