Hi Rob,
Would you agree Perforce has 'password' and 'ticket' authentication?
For ticket authentication, the ticket is retrieved from the p4 login command at line 618 of AbstractLoginTemplate.
One can see that when using ticket authentication, whatever is passed in via stdin is ignored.
$ echo "" | p4 login -a -p
A6A9E2785DEXXXXXXXXXXXXXXXXXXXX
$ echo "AnyPassword" | p4 login -a -p
A6A9E2785DEXXXXXXXXXXXXXXXXXXXX
The ticket is returned for later use by the plugin. The above is exactly what's occurring at line 634.
Most users leave the 'password' field blank, as they should, but some users enter their password. Both produce the same result, but the latter is a security concern which I'm wanting to address by removing the option to enter a password.
Regards,
Brian
Please provide a link to the documentation describing P4's Kerberos support. I am not seeing any documentation that would suggest it's supported in any way on the client side. P4 tickets are supposed to be provided in the password field themselves, and are no way ignored by p4.
If this is a custom client or login trigger, then we cannot support that in the perforce plugin, as removing the p4 password will break the plugin.