API help with ticket expiry

[Douglas E. Engert]

Keagle, Chuck wrote:

> If the Credential is available, I'm trying to figure how long it will be before 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.
> 
> Maybe the klist source will show me what needs to be done.  If you don't have a Credential it shows none.  If you have a Credential, it shows the expiration date/time.
> 

If you get a ticket good for 8 hours, and renewable for 3 days:
    kinit -l 8h -r 3d user at realm
the MIT klist will show Valid starting, Expires and renew until times.

The Heimdal klist -v will these as well.

Renewable might be good for batch jobs.


> -----
> Not all who wander are lost! 
> 
> Chuck Keagle               |     ----  ___o  |  chuck.keagle at boeing.com 
> Enterprise Servers         |  -------  \ <,  |  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 at 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 the problem.  If there are no credentials available, you
> can't magically generate them.
> 
> --Ken
> ________________________________________________
> Kerberos mailing list           Kerberos at mit.edu
> https://mailman.mit.edu/mailman/listinfo/kerberos
> 
> 

-- 

  Douglas E. Engert  <DEEngert at anl.gov>
  Argonne National Laboratory
  9700 South Cass Avenue
  Argonne, Illinois  60439
  (630) 252-5444