GlobalProtect actually tries to cache and re-use credentials provided by the user for portal and the gateway. Meaning, the credentials you entered for the portal would be re-used for the gateway connection. Because you use two different authentication profiles for portal and gateway, the authentication with the cached credentials fails and we prompt you to enter the password again, or in your case the SecurID PIN and Tokencode. This is actually expected behaviour. Though, unlike other applications we don't try to authenticate over and over again with those cached credentials, hoping that the authentication server would magically accept those credentials. Instead, we only try once and the prompt the user. We are working on some improvements on improving the product experience so that you won't see an error messages due to a failed first authentication. But for now, this is why you see the behaviour you described. Functionally, it should work fine though, with the log errors being an annoyance right now.
... View more