topic Re: Identity Awareness - Browser Based Authentication change accessibility in Firewall and Security Management

Identity Awareness - Browser Based Authentication change accessibility

michael3 — Mon, 06 Feb 2023 15:37:12 GMT

Hello,

We have Identity Awareness with Browser based authentication activated, which is accessible "through all Interfaces". We want to change this to the option "According to the Firewall Policy". What exact rules are needed here? There is no further explantion for the option in the SmartConsole help. I also couldn't find anything online.

When we activated the "According to the Firewall Policy" option once, the Portal was not accessible at all anymore, although there was a rule with the action "accept (display captive portal)".

We're running R81.10 T45.

Re: Identity Awareness - Browser Based Authentication change accessibility

PhoneBoy — Mon, 06 Feb 2023 22:32:45 GMT

TCP port 443 (https) is what is required for Captive Portal to work.
The rule should just have a simple Accept action (not with Display Captive Portal).

Re: Identity Awareness - Browser Based Authentication change accessibility

michael3 — Tue, 07 Feb 2023 17:45:29 GMT

Hallo,

thx for your reply, so i would a need a rule like:
Usergroup1 -> GatewayIP (where the Captive portal (should) run) : https accept

But how do I acheive that different User objects are only allowed to access a certain destination then? Does this also mean there are no redirects anymore and customers directly have to enter the Gateway IP or DNS to the Browser?

At the moment we have rules like the following scheme:

Users1 -> DestinationIP1 : services accept(display captive portal)
Users2 -> DestinationnetworkX : services accept(display captive portal)

In the Users Object, LDAP Groups, possible source networks etc are defined.
If the destination is a http site, I'm automatically redirected to Identity Portal.

I mean a redirect is not necesarry, just that I can define different usergroups with different destinations and services

Re: Identity Awareness - Browser Based Authentication change accessibility

PhoneBoy — Tue, 07 Feb 2023 21:25:43 GMT

The rule I described allows the Captive Portal to be reached when "According to Firewall Policy" is used.
You still need to have your other rules in place.
Also, HTTPS Inspection must be enabled in order for redirects to occur when the destination site is HTTPS.

Re: Identity Awareness - Browser Based Authentication change accessibility

michael3 — Thu, 09 Feb 2023 17:10:26 GMT

Hallo,

thank you very much, I now tried this successfully 🙂

I have one final question: What would I have to change, sucht that there isn't any redirect? So people just have to know that they browse to the Gateway (Identity Portal) first and then after successful login, they can do what they are allowed according to the rules.

Re: Identity Awareness - Browser Based Authentication change accessibility

PhoneBoy — Thu, 09 Feb 2023 19:07:08 GMT

Yes, users can browse to a specific URL on the gateway and authenticate manually.
You can see the precise URL for your environment and configure various aspects of it here: