Diego,
Thanks for your help and guidance on this… The end-system is getting the reply
from Google with the authorization code – the Portal URL in the config that
ends in ‘/callback’. However, the hostname of the pf server is not being
resolved. If I replace the hostname.domain with the IP
Hi.. those errors are not errors. They are jus the logs of pfdns and its
still related to the user trying / reaching google.
you should look at the logs (especially packetfence.log) for any other
messages around the time. Most of the log messages SHOULD have the mac
address of the device trying
Hello Nicolas, here is the Output:[root@nac3 ~]# /usr/local/pf/bin/pfcmd service pf status Service Status PID
Again, apologies for my ignorance on this…
When I created the Oauth credentials in the Google Developer site, I did not
enable an API. I’m thinking I missed doing that. Since I’m just trying to
authenticate users and not accessing anything within GSuite or anything else
along those lines,
let me check what I have configured. But i think you do need n API enabled.
On Fri, Apr 24, 2020 at 11:12 AM Bill Handler wrote:
> Again, apologies for my ignorance on this…
>
>
>
> When I created the Oauth credentials in the Google Developer site, I did
> not enable an API. I’m thinking I
Diego,
Thanks for the pointers. The logs appear to be now located in the
/usr/local/pf/logs directory. There is no logs folder in the /usr/local/pf/var
directory.
I ran the restart command and tried to log in via Google again… Rechecked the
logs as I did before (grep OAuth), ran it a
