[p4] long ticket expiration

[David Weintraub]

Does the LDAP process affect all logins, or only those Perforce
accounts that also have a Windows account? For example, if you create
a user called "build", would this use be able to log into Perforce if
there was no Windows account by that name?

If that is the case, then you could create a "build" account just to
run scripts. This account could be a long lived account with very
limited user rights (no rights to submit any changes, etc.) Since this
user isn't under LDAP policy, you don't have to worry about its
password expiring.

Another choice is to lengthen the logout period from 12 hours to 20
hours. Each time the "p4" command is called, the Perforce ticket is
lengthened by 1/3 of the logout time. So, if someone runs Perforce at
5pm, the ticket will still be good at 4am when the script starts.

On 1/8/07, steve at vance.com <steve at vance.com> wrote:
> I generally create an infinite password and appeal for the automated
> process to be an exception from the password change policy. If that won't
> work, then you need to create the ticket when the password changes.
>
> Steve
>
> Original Message:
> -----------------
> From:  Jamie.Echlin at barclayscapital.com
> Date:   Mon, 8 Jan 2007 10:16:49 -0000
> To: perforce-user at perforce.com
> Subject: [p4] long ticket expiration
>
>
> Morning,
>
> One group here requests that I set them to never expire, I think because
> partly they don't like the hassle of logging on, and also their scripts
> have been failing when run at 4am.
>
> Being fairly new to Perforce I'd like to ask for some advice, what do
> other people do?
>
> Should I tell them to "login" in their scripts, but the problem then is,
> we use the integration with LDAP, and when their windows passwords
> expire (3 months), they will forget to change their scripts, and end up
> locking their accounts.
>
> Or, I was thinking set it to 24 hours so their nightly scripts will
> succeed? But then, (I don't think tickets get automatically extended are
> they?) it will timeout from the previous day possibly soon after they
> start working, so I was thinking 22 hours?
>
> Infinite expiration just seems wrong, although I'm not sure why. Perhaps
> because they could pass the ticket around and an infinite ticket is more
> valuable than a 24 hour one?
>
> Anyway, you see my problem. Thanks in advance for any pointers.
>
> cheers, jamie
> ------------------------------------------------------------------------
> For more information about Barclays Capital, please visit our web site at
> http://www.barcap.com.
>
> Internet communications are not secure and therefore the Barclays Group
> does not accept legal responsibility for the contents of this message.
> Although the Barclays Group operates anti-virus programmes, it does not
> accept responsibility for any damage whatsoever that is caused by viruses
> being passed.  Any views or opinions presented are solely those of the
> author and do not necessarily represent those of the Barclays Group.
> Replies to this email may be monitored by the Barclays Group for
> operational or business reasons.
> ------------------------------------------------------------------------
>
> _______________________________________________
> perforce-user mailing list  -  perforce-user at perforce.com
> http://maillist.perforce.com/mailman/listinfo/perforce-user
>
>
> --------------------------------------------------------------------
> mail2web - Check your email from the web at
> http://mail2web.com/ .
>
>
> _______________________________________________
> perforce-user mailing list  -  perforce-user at perforce.com
> http://maillist.perforce.com/mailman/listinfo/perforce-user
>


-- 
--
David Weintraub
qazwart at gmail.com