Just wondering if someone can shed some light on link persistence when redirecting through Palo Alto cloud identity engine.
In our previous config which was Local user authentication based, an automatically generated link which would open a response page on a server within our AWS VPC could be clicked and it would take us to the local GP portal login page. Once the user authenticated, it would move on to the originally clicked link.
Original link which worked after authentication > "https://vpn.example.old/https/my.same.server/pause/eyJhbGciOiJFUzI1NiJ9.eyJpZCI6MjUsImVjIjo1LCJpYXQiOjE2NTYxMTQ3OTMsInN1YiI6IjIyMDYwNyIsImF1ZCI6Ii9wYXVzZSIsImV4cCI6MTY1NjcxOTU5Mn0.z0rThjKsfGnMbeJAtzLTAaHEdMRJtFzb2A0tKB35K40i5Midiv-lvqod-rpefC6oMDNiK6z6H-bqdpHYgwyG5w"
The new link (which is a new VM series firewall with a different address and utilizing cloud identity engine) >"https://vpn.example.new/https/my.same.server/pause/eyJhbGciOiJFUzI1NiJ9.eyJpZCI6MjUsImVjIjo1LCJpYXQiOjE2NTYxMTQ3OTMsInN1YiI6IjIyMDYwNyIsImF1ZCI6Ii9wYXVzZSIsImV4cCI6MTY1NjcxOTU5Mn0.z0rThjKsfGnMbeJAtzLTAaHEdMRJtFzb2A0tKB35K40i5Midiv-lvqod-rpefC6oMDNiK6z6H-bqdpHYgwyG5w"
The new link would redirect to cloud identity engine then Microsoft login page. After the user logs in, it goes straight to the Home page of global protect portal rather than the desired link. With local identification, after user authenticates it would go to the desired page.
Once authenticated the user can click on the same link again and it would work then.
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 LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!