Global Protect Caching Username for Secondary Authentication

Reply
Highlighted
L1 Bithead

Global Protect Caching Username for Secondary Authentication

Hi,

 

I have a slight issue whereby I am operating 2FA for my SSL users utilising Global Protect.  The initial authentication is using Single Sign On techniques to the domain controller with the secondary authenication requiring Entrust token input before connecting the the VPN.

 

Both work well, however upon connecting to the SSL VPN, the users are prompted with the authentication dialogue box for the Entrust username and password but the username is always pre-populated with the initial authentication credentials from domain credentials.  I'd like it so that the username entry is not pre-populated and is blank when offered to the users.

 

I have read numerous Palo Alto briefs on how to remove but no joy....any help appreciated.

 

Thanks

Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

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!