Allow passthru for OCSP/CRL checks for the cert in question. Most are
already allowed.
On Wed, Jul 1, 2015 at 3:10 PM, Leja, Maciej wrote:
> Thanks for the response, that was my problem originally but I fixed
> that. Now going to the admin portal shows the chain (host cert > inCommon
> > Use
Thanks for the response, that was my problem originally but I fixed that. Now
going to the admin portal shows the chain (host cert > inCommon > UserTrust RSA
> AddTrust External CA root) so everything looks good on admin site. But when
getting to the portal when I have no internet connectivity
Did you include the certificate chain ? i had to include the issuing
(intermediate) CA to get rid of the warnings. The root-CA was already
trusted on the clients (RapidSSL) but the intermediate had to be included
for the clients to trust my certificate.
Not sure if this applies to your situation.
Hey folks,
I set up a new legit ssl cert for the PF box – working for the admin interface
but users behind the captive portal are not allowed to validate it (because
they’re not online)….
Any ideas how to get around this so users don’t get the error in their browser
when hitting the captive po
Hi,
How can I disable DHCP detection in one of PF's networks?
I'm seeing nodes detected on Mgmt interface but I don't need it.
I'm running PF ZEN 5.1 updated to 5.2 with inline enforcement.
Thanks in advance.
Regards,
Leo
Hi,
We have one last remaing issue (for the moment.) in our test-setup:
procurve 5400, 802.1x authentication, samba4 AD backend, packetfence 5.2.0.
I have added two user sources: ad-users (sAMAccountName) and
ad-computers (servicePrincipalName) on list number 2 and 3, below the
'default lega
