Options for Abfab-based Kerberos pre-authentication
draft-perez-abfab-kerberos-preauth-options-01
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Alejandro Pérez-Méndez , Josh Howlett | ||
Last updated | 2012-09-13 (Latest revision 2012-03-12) | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Expired | |
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
Kerberos is widely used for authentication within organisations. It is not, however, commonly used for authentication between domains or realms ("cross-realm operation"). Abfab is a new architecture, based on the AAA framework, that provides a mechanism for federating authentication between realms. AAA protocols are already widely used for federating authentication for network access scenarios today. It has been proposed that Abfab could be used to provide a mechanism yielding cross-realm functionality for Kerberos. This document discusses two alternative models with the aim of informing and facilitating discussion.
Authors
Alejandro Pérez-Méndez
Josh Howlett
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)