[p4] Scripting and ticket authentication

[Shawn Hladky]

Currently we do the following:
use P4CONFIG files
in the p4config set P4PASSWD to a ticket value that doesn't expire for a
long time.

I've been prototyping a new strategy:
Set P4TICKETS to a centralized remote share.  Access to the share is
restricted by the system account (NT in our case) running the script.
On a secure server, run a script to update the ticket on the central server
(p4 logout -a & p4 login -a) daily.

The theory behind this is that the NT accounts should already be secure, and
you'll need that secure access to get a current ticket.  The downside is
that fileshare becomes a single point of failure for the scripts, and
cross-platform stuff gets tricky.


On 7/17/07, Bob Van Zant <bob at norcalttora.com> wrote:
>
> I started playing with the P4PASSWD env variable just today. You can put
> the
> result of `p4 login -p` into the P4PASSWD variable. I assume that is valid
> for as long as the ticket generated by p4 login is? Anyway, once that
> variable is set you can skip the actual p4 login. I think.
>
> This might help more than I just did:
>
> http://www.perforce.com/perforce/doc.052/manuals/cmdref/env.P4PASSWD.html
>
> -Bob
>
>
> On 7/17/07 11:30 PM, "Jamison, Shawn" <sjamison at ciena.com> wrote:
>
> > I know this has been asked before but I cant seem to find it.
> >
> > Is there a way to get around the prompt for windows and unix scripts
> > that need to do a p4 login?
> >
> > It would be nice if I could supply a password in the script to obtain a
> > ticket.
> >
> > Thanks
> > -Shawn J>
> >
> > _______________________________________________
> > perforce-user mailing list  -  perforce-user at perforce.com
> > http://maillist.perforce.com/mailman/listinfo/perforce-user
> >
>
> _______________________________________________
> perforce-user mailing list  -  perforce-user at perforce.com
> http://maillist.perforce.com/mailman/listinfo/perforce-user
>