Architecture for Implementing Network Single Sign-On
draft-goenka-single-sign-on-arch-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Vishal Goenka | ||
| Last updated | 2000-03-06 | ||
| 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
There are several different single sign-on (SSO) solutions offered by various software vendors today. All such solutions require applications to be written to a vendor specific API. In view of a lack of industry wide standard for SSO APIs, application developers find it almost impossible to SSO enable their applications to work with any vendor solution. This document presents alternative SSO implementation architecture that allows applications to be transparently enabled for SSO. Further, it allows different SSO solutions to interoperate with relatively little effort.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)