/Webcard.cfm?id=73990
> -Original Message-
> From: Ken Hornstein [mailto:[EMAIL PROTECTED]
> Sent: Friday, September 29, 2006 11:24 AM
> To: Keagle, Chuck
> Cc: kerberos@mit.edu
> Subject: Re: API help with ticket expiry
>
> >If the Credential is available,
>If the Credential is available, I'm trying to figure how long it will be be
>fore it expires. I'm not counting on magic. Just looking at, if I already
> have a Credential, I might not have to generate a new one.
But ... the existing APIs already give you that (the ones I talked about).
I have
;, | work: (425)865-1488
> High Performance Computing | - ( )/ ( ) | cell: (425)417-3434
>
>
>
> From: Ken Hornstein
> Sent: Thu 9/28/2006 10:33 PM
> To: Keagle, Chuck
> Cc: kerberos@mit.edu
> Subject: Re: API help with ticket expiry
>
>
>
formance Computing | - ( )/ ( ) | cell: (425)417-3434
From: Ken Hornstein
Sent: Thu 9/28/2006 10:33 PM
To: Keagle, Chuck
Cc: kerberos@mit.edu
Subject: Re: API help with ticket expiry
>When the next batch job is submitted, it comes from a new execution of
>the submit program.
Well, this is th
>When the next batch job is submitted, it comes from a new execution of
>the submit program.
Well, this is the problem. If there are no credentials available, you
can't magically generate them.
--Ken
Kerberos mailing list Kerberos@mit.ed
> From: Ken Hornstein [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, September 27, 2006 9:14 PM
> To: Keagle, Chuck
> Cc: kerberos@mit.edu
> Subject: Re: API help with ticket expiry
>
> >I have been able to create the ticket using encrypted
> username/password
> >
>I have been able to create the ticket using encrypted username/password
>and am now working on making sure the ticket doesn't expire before the
>job ends. Granted, this isn't the safest mechanism, but users don't
>want jobs to abort if ticket expires when they are not around.
>
>krb5_timeofday()
