[22312] in Kerberos
RE: Commit password change
daemon@ATHENA.MIT.EDU (Digant Kasundra)
Mon Aug 30 12:54:44 2004
Message-ID: <CEE4E6ECB6C98C4281D09A17EC3DC0ED084BF2C2@exchange.uta.edu>
From: Digant Kasundra <digant@uta.edu>
To: John Hascall <john@iastate.edu>
Date: Mon, 30 Aug 2004 11:52:25 -0500
MIME-Version: 1.0
Content-Type: text/plain
cc: kerberos@mit.edu
Errors-To: kerberos-bounces@mit.edu
Thanks. I'll take a look into this.
> -----Original Message-----
> From: John Hascall [mailto:john@iastate.edu]
> Sent: Monday, August 30, 2004 11:42 AM
> To: Digant Kasundra
> Cc: kerberos@MIT.EDU
> Subject: Re: Commit password change
>
>
>
> > Can someone tell me where in the code a password change is actually
> > committed? I see a handful or wrappers and related
> functions but I'm
> > curious is there is one single point where a
> principal/password pair
> > are written.
>
> Almost. You'll want to look in
> src/lib/kadm5/srv/svr_principal.c We put hooks in these functions:
> kadm5_create_principal_3()
> kadm5_delete_principal()
> kadm5_rename_principal()
> kadm5_chpass_principal_3()
>
> > My plan is to hook into that function to send
> principal/password pairs
> > to an external auth service so that passwords can stay in sync.
>
> Several of us have already done this. If you search the
> archives you'll probably find something that will help you.
>
>
> John
>
________________________________________________
Kerberos mailing list Kerberos@mit.edu
https://mailman.mit.edu/mailman/listinfo/kerberos
