Here use case and wondering if this is feasible.
1. User Bob is already authenticated and connected(tunnel VPN) to firewall A with GlobalProtect with his account "Bob".
2. User Bob need to access critical ressource behind the same firewall A with, however, his privilege account "Bob-Priv".
Problem, its look like the authentication policy is never triggered because user Bob is already authenticated with account "Bob".
Is there a way to achieve this ?
set up an authentication policy for 'known-user' which will trigger a new authentication window only if the user is already known through app-id
It's not working.
The user is never triggered with the captive portal auth page. I think, this is because the firewall is already aware of Bob account that came from User ID Agent. However, I want that auth rule is triggered to let user login with his priviledge account.
Is the rule matching the proper source zone/subnet, destination zone/subnet etc?
Have you tried setting set 'user' field to any?
If that also fails, try 'select' and set 'bob' as the user that needs to authenticate
Okay, Captive Portal was not triggered because the destination was HTTPS, and SSL decryption is required for Captive Portal to "redirect" HTTPS traffic.
Also, notice that UserID database is always updated with latest user account logged. That could cause problem in "big" environment where multiple accounts (normal, priviledge ..) are required to touch specific ressources. I think that dedicated firewall(s) or VSYS isolated from the "normal USERID Database" could be a solution to front specific secure environment, like critical database, PCI... etc.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the Live Community as a whole!
The Live Community thanks you for your participation!