Authentication Policy with Captive Portal using Session Cookie

[santonic]

Customer has authentication policy with web-form as authentication profile and 60 minutes timeout.

Captive Portal has both timers at 60 minutes and uses Session Cookies with 60 minutes timeout.

However if a user hits refresh for the authenticated (https) session less than 60 minutes after succesful authentication he gets prompted to re-authenticate. Is this expected behaviour? In that case does session cookie authenticate single (https) session only?

[santonic]

Nobody has any info about this?

[Remo]

Hi @santonic 

Is the cp configured in redirect mode? Was the browser open from the time the user authenticates till he hits refresh? Whem this happens is there still an ip-user-mapping entry when this happens? Is this issue reproducable all the time with every user/computer/browser?

[santonic]

Hello.

Yes, CP is in redirect mode. In this case it's used to force MFA authentication (not from PA supported list) connected to PA over radius protocol. 

Yes, user has the browser open since first authentication and according to customer's words it's happening to multiple users. I haven't been monitoring User-ID mapping during refresh yet. 

Was just wandering what is the default behaviour, what does the cookie authorise: single session or multiple sessions from that IP address for the period of time.

[santonic]

The issue is that User-ID agents who are getting info from AD servers overwrite the info about user on specific IP from which the user authentcated through authenticaion policy. Authentication policy via captive portal uses different authentication server (MFA as radius server) and different users.