[7645] in Kerberos

home help back first fref pref prev next nref lref last post

Re: Kerberos AUTH from a Mac App

daemon@ATHENA.MIT.EDU (Robert Currey)
Tue Jul 16 16:43:07 1996

To: kerberos@MIT.EDU
Date: Tue, 16 Jul 1996 13:11:19 -0700
From: Robert Currey <curreyr@halcyon.com>
Reply-To: curreyr@halcyon.com

John Gardiner Myers wrote:
> 
> Kerberos is a single-signon system.  The user runs a separate
> application/driver to authenticate to the Kerberos service.  The
> various client programs then talk to the Kerberos driver to get
> the bits they need to authenticate to Kerberos services.
> 
> Just linking in a library doesn't work, since then the user would have
> to type their password into every single client application.  There
> has to be a driver, so the various client applications can share the
> user's Kerberos authentication.
> 
> There are three major Kerberos implementations for the Macintosh:
> AuthMan, KClient, and MacLeland.
> 
> Each of the three has its own native API.  Some support the API's of
> the other implementations.
> 
> My advice would be to implement to the KClient API, using any of the
> three implementations.
> 

Thanks for the summary ....

I now understand why the driver is needed and will start investigating
my further options ...

Robert Currey

home help back first fref pref prev next nref lref last post