[p4] scripting with ticket-based authentication?

Johan Nilsson johan.nilsson at esrange.ssc.se
Thu Oct 6 23:45:17 PDT 2005


> -----Original Message-----
> From: perforce-user-bounces at perforce.com 
> [mailto:perforce-user-bounces at perforce.com] On Behalf Of Jeff Grills
> Sent: den 6 oktober 2005 21:27
> To: John.Davis at sophos.com; perforce-user at perforce.com
> Cc: Amanda.Culver at sophos.com
> Subject: RE: [p4] scripting with ticket-based authentication?
> I've been in this exact situation before.  Perforce ticket 
> expiration times are based on groups, and users in multiple 
> groups get the longest timeout of any of the groups.  You can 
> also set the timeout for a group to be 0, indicating that the 
> ticket never expires.  We dedicated a perforce license for 
> the automated scripts (you should be able to get a free 
> license for an automated user from perforce - just ask!).  We 
> then put that automated user in a group consisting of only 
> themselves and gave that group a ticket timeout of 0.  Then 
> we just simply issued a single "p4 login" on the automated 
> machine to get a ticket that will never expire.  After that, 
> the password for the automated user is no longer needed for 
> anything.  The automated scripts never have to deal with 
> embedded passwords or anything else - the ticket always works.

FWIW I've also done exactly the same thing and so far it works just
fine. I've also made sure that this user can only access the depots from
the local machine using 'p4 protect'.

Just as a side note, setting the timeout field to '0' for a group
requires 2005.1, IIRC.

// Johan

More information about the perforce-user mailing list