The system I'm doing a POC with uses local accounts in production on both linux
and windows boxes, which are headless.
On linux, k5start with a keytab for the afs user works fine for keeping a fresh
token available for the local account.
On windows, I'm having problems getting similar functionality.
First attempt was a scheduled task as the local user to kinit with the keytab
and then aklog .. it runs without errors but other shells (new or existing) for
the same user don't see any tickets (klist) or tokens. Separate caches?
Second attempt was with Network Identity Manager, which would be perfect if I
can figure out how to make it use my keytab instead of typing a password.
Anyone have another solution?
JohnD
The content of this e-mail message and any attached files transmitted with it
are to be treated as confidential information and are intended solely for the
use of the individual or entity to whom they are addressed. If the reader of
this e-mail is not the intended recipient or his or her authorized agent, the
reader is hereby notified that any reproduction, distribution, or disclosure of
this e-mail is prohibited. If you have received this e-mail in error, please
notify the sender by replying to this message and delete this e-mail
immediately.***1010data, Inc. and its affiliates ("1010data") are not
responsible for any advice concerning the use of its software or services or
the data manipulated by its software, except to the extent 1010data has
specifically undertaken such responsibility in a validly binding contract.
1010data shall have no responsibility for any decision concerning the
appropriate method of use or application of its software or services or the
data therein in connection with any transaction. Any decision concerning how,
where and when to use this facility remains the sole responsibility of the user.