Https traffic passing through Security Gateway does not match Captive Portal redirection rule in Application & URL Filtering (APPI) rulebase.
Cause
HTTPs traffic must be first accepted in main Security Gateway rulebase.
Solution
Create regular Accept rule for https traffic in Security Gateway rulebase (AccessRole cannot be used here yet).
Once target https traffic is accepted then it will be forwarded to the APPI rulebase to match Captive Portal redirection rule (Here you can use AccessRole in the rule).
Note: HTTPS Inspection is required for redirecting to Captive Portal on HTTPS sites.
C)
0
0
According to CSSA’s documentation it’s {D}
0
0
R76 document and I think still applies for R77:
https://sc1.checkpoint.com/documents/R76/CP_R76_IdentityAwareness_AdminGuide/62050.htm
0
0
Although, according to this sk101244:
Symptoms
Https traffic passing through Security Gateway does not match Captive Portal redirection rule in Application & URL Filtering (APPI) rulebase.
Cause
HTTPs traffic must be first accepted in main Security Gateway rulebase.
Solution
Create regular Accept rule for https traffic in Security Gateway rulebase (AccessRole cannot be used here yet).
Once target https traffic is accepted then it will be forwarded to the APPI rulebase to match Captive Portal redirection rule (Here you can use AccessRole in the rule).
Note: HTTPS Inspection is required for redirecting to Captive Portal on HTTPS sites.
So I guess {C} is correct after all.
0
0
C
0
0