Login process for the user
Users are authenticated in one of two ways:
-
The user logs in explicitly using the
p4 logincommand.The user enters a p4 command, and the command requires that the user be authenticated. If the user is not already authenticated, the command will prompt for login. If the login is successful, the original command continues.
To log in to
Helix Server, the user
obtains a ticket from the server by using the p4
login command:
$ p4 login
The user is prompted for a password, and a ticket is created for the
user in the file specified by P4TICKETS. The user can extend
the ticket’s lifespan by calling p4 login while
already logged in; this extends the ticket’s lifespan by 1/3 of its
initial timeout setting, subject to a maximum of the user’s initial
timeout setting.
The
Helix Server
service rate-limits the user’s ability to run p4
login after multiple failed login attempts. To alter this
behavior, set dm.user.loginattempts to the maximum allowable
failed login attempts before the service imposes a 10-second delay on
subsequent login attempts.
By default,
Helix Server
tickets are valid for the user’s IP address only. If the user has a
shared home directory that is used on more than one machine, the user can
log in to
Helix Server
from both machines by using p4 login -a to create a
ticket in the home directory that is valid from all IP addresses.
Tickets can be used by multiple clients on the same machine so long as they use the same user and port.
The auth.csv log is used to log the results of
p4 login attempts. If the login failed, the reason
for this is included in the log. Additional information provided by the
authentication method is included in the log entries.
