|Title||Interactions with Perforce ticket system not documented|
|Assigned user||Nick Barnes|
|Description||The AG has no information or advice on using the P4DTI with Perforce "tickets" (e.g. to allow a Perforce server security level of 3).|
|Analysis||Perforce introduced a new authentication system using "tickets" in P4 2003.2. A ticket is obtained by logging in (with "p4 login") and can be used in place of a Perforce password. This system adds some security to the plain password system because the tickets expire (in 12 hours by default; this can be set on a per-group basis). Perforce also has "security levels" for enforcing password and ticket security. Levels 0-2 control password strength; level 3 requires the use of tickets. In P4 2004.2 beta this system has become documented in the P4 SAG (chapter 3; also in "p4 help login", etc).|
The P4DTI can use a ticket for the replicator user, simply by specifying the ticket in place of a password in config.py. This has to be done manually by the administrator, and the replicator user must be given a very long ticket timeout value (using Perforce groups) as the replicator has no means of handling ticket expiry.
The AG needs to cover this.
See also job000969 about a longer-term improvement to the P4DTI to automate ticket handling.
|Created by||Nick Barnes|
|Created on||2004-07-20 11:44:28|
|Last modified by||Nick Barnes|
|Last modified on||2004-07-20 17:05:53|
|History||2004-07-20 NB Created.|
|107080||closed||2004-07-20 17:05:53||Nick Barnes||Add information about Perforce tickets to the AG.|