ks,
>
>
>
> Bill
>
>
>
>
>
> *From:* Diego Garcia del Rio
> *Sent:* Wednesday, April 29, 2020 11:48 AM
> *To:* Bill Handler
> *Cc:* Jonathan Nathanson ;
> packetfence-users@lists.sourceforge.net
> *Subject:* Re: [PacketFence-users] Google oauth2 -
>
10:11 AM
To: Bill Handler
Cc: Jonathan Nathanson ;
packetfence-users@lists.sourceforge.net
Subject: Re: [PacketFence-users] Google oauth2 - Behavior/Troubleshooting -
http vs https
Hi Bill
Interesting that of using http it works. I used publicly signed certs for my
portal. Self signed will just be
onder
>> why I’m not getting the same pop-up or it’s not accepting the previously
>> accepted self-signed cert for that oauth page.
>>
>>
>>
>> Thanks,
>>
>>
>>
>> Bill
>>
>>
>>
>>
>>
>> *From:* Die
e same pop-up or it’s not accepting the previously
> accepted self-signed cert for that oauth page.
>
>
>
> Thanks,
>
>
>
> Bill
>
>
>
>
>
> *From:* Diego Garcia del Rio
> *Sent:* Wednesday, April 29, 2020 10:11 AM
> *To:* Bill Handler
> *Cc:* Jonath
Hi Bill
Interesting that of using http it works. I used publicly signed certs for
my portal. Self signed will just be chaos for the end users unless you can
push your root ca to the the devices beforehand (a managed fleet, which is
not my case)
Now it's clearer that you used the IP and it
Diego,
Our internal DNS is just set for our data vlan – currently there is no DNS
record for the PF server in our internal DNS server. The registration VLAN
only lives on the switch directly connected to NIC 2 on the PF server and on my
test switches that my testing end-systems are connected
