Hi,
Have been testing heartbeat aurthentication with XG17.5, Central, Win 10 and 2012 Active Directory.
The scenario is as follows...
Log on to W10 client as local (non AD) user that is unauthenticated on the XG.
Firewall policy to match user (and present portal to unauthenticated user) presents captive portal. Log into portal with domain credentials and authenticate OK to browse web.
Log off W10 client and log on as domain user which authenticates with XG using heartbeat.
User that was logged on via captive portal is removed from Live Users list in XG.
Firewall policy to match user (and present portal to unauthenticated user) allows web browsing.
Log domain user off W10 client and log back on as local (non AD) user that is unauthenticated on the XG.
Web traffic is allowed as the heartbeat authenticated user is not removed from the live user list in XG.
Had to shut down W10 guest to automatically remove the user from heartbeat authenticated user from XG.
Anyone else seen similar or is that expected behaviour.
Cheers
Jim
This thread was automatically locked due to age.