Kerberos is a network authentication system which is available for Unix, Windows, Macintosh, and I'm sure lots of other platforms.
How does this relate to
OpenAFS?
OpenAFS uses Kerberos to perform strong authentication for clients connecting to the AFS filespace. If you're new to Kerberos, you should take a look at the Kerberos FAQ located at
http://www.nrl.navy.mil/CCS/people/kenh/kerberos-faq.html. For the impatient, a quick list of useful Kerberos-related terms will be available at
KerberosTerms.
Note that there are two versions of Kerberos in wide usage. The latest is
KerberosV, but AFS, for historical reasons, uses a modified version of Kerberos 4 (see
KaServer). However, AFS can be integrated into a
KerberosV realm, and in fact is highly suggested for any new installations of AFS. See
SettingUpAuthentication?.
Installing
KerberosV along with
OpenAFS will provide the basis for many other very cool features, such as a single repository for all authentication information for an administrative domain, integration with the Windows 2000/XP login mechanism, and even single-sign-on capability. Note that the further down you get in that list, the harder things become.
The installation documentation on the
OpenAFS web site unfortunately does not include any information on integrating AFS into a
KerberosV realm. (Work on install document & gotchas page later)
To compile
OpenAFS with
KerberosV support you need to use the --with-krb5-conf=/path/to/krb5-config flag to configure.
If you're using
KerberosVMIT versions 1.2.6 or later, you'll need to add a section to
krb5.conf on the krb524d host if you wish to continue using old-style
KerberosIV? ticket derived tokens.
[appdefaults]
afs_krb5 = {
REALM.NAME = {
afs = false
afs/cell.name = false
}
}
Where NAME and cell.name are the names of your
KerberosRealm? and
AFSCell? respectively.
If you already have a working AFS cell using
KaServer, check out
DerrickBrashear's document for converting from the
KaServer to
HeimdalKTH here:
file:/afs/andrew.cmu.edu/usr/shadow/ka2heim.txt
For now a few links... explanations to follow later:
Some other issues to explain:
- PAM modules available for K5
- Admin differences between various K5 implementations
- krb524d -- which uses a K5 TGT to produce a V4 AFS service ticket which the CacheManager? needs. It does not need to run on the same machine as the KerberosV server but just needs access to the AFS principal's key. This is not needed for HeimdalKTH which implements V4 and V5 services, but is for MIT and ActiveDirectory.
- encryption types -- this is a per key property and V5 supports several (while V4 only supported one, namely what V5 calls des-cbc-crc). However, this is not the V5 default (which I think is des3) so you need to ensure that the AFS principal uses des-cbc-crc.
- StringToKey differences
Links
Main Site
--
TedAnderson - 22 Jan 2002
--
DerrickBrashear - 23 Jan 2002
--
TedAnderson - 23 Jan 2002
--
JasonGarman? - 30 Jan 2002
--
TedAnderson - 31 Jan 2002
See
HeimdalKTH,
ActiveDirectory,
KerberosDCE?,
AuthCommands,
SettingUpAuthentication?.