[2150] in Kerberos
Re: New User Accounts
daemon@ATHENA.MIT.EDU (larry hughes)
Wed Sep 2 16:22:26 1992
Date: 2 Sep 92 19:53:28 GMT
From: hughes@logos.ucs.indiana.edu (larry hughes)
To: kerberos@shelby.Stanford.EDU
In article <9209020104.AA25528@windsail.nersc.gov> ramus@nersc.gov (Joe
Ramus) writes:
> How do other sites manage new accounts and assigned passwords?
At IU, we used a "volunteer" approach. If you don't volunteer,
you don't get the benefits of using the distributed workstation
services.
We wrote an application that users run from a single timeshared
system (hence we know who they are already). The program queues
the username (which becomes the principal name) and password
in a secure way, where it is later processed in batch. I might
add that we obviously maintain a strict dictionary of usernames
across our timeshared systems. :-)
The batch job performs a kinit to a privileged principal, and
sends the principal name and password (all encrypted of course)
to a server process running on the master Kerberos server. If
you look in the source for kdb_edit, you'll see that there's
actually very little code required to add a principal into the
Kerberos database.
Cheers,
//==================================================================\\
|| Larry J. Hughes, Jr. | hughes@indiana.edu ||
|| Indiana University | "The person who knows everything ||
|| University Computing Services | has a lot to learn." ||
\\===================================================================//
