Draft LDAP Single Sign On Token Processing
draft-wibrown-ldapssotoken-02

Document Type Active Internet-Draft (individual)
Last updated 2017-02-27
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Internet Engineering Task Force                                 W. Brown
Internet-Draft                              Red Hat Asia-Pacific Pty Ltd
Intended status: Standards Track                           S. Sorce, Ed.
Expires: August 31, 2017                                   Red Hat, Inc.
                                                         K. Andrews, Ed.
                                              The University of Adelaide
                                                       February 27, 2017

               Draft LDAP Single Sign On Token Processing
                     draft-wibrown-ldapssotoken-02

Abstract

   LDAP Single Sign On Token is a SASL (Simple Authentication and
   Security Layer RFC 2222 [RFC2222]) mechanism to allow single sign-on
   to an LDAP Directory Server environment.  Tokens generated by the
   LDAP server can be transmitted through other protocols and channels,
   allowing a broad range of clients and middleware to take advantage of
   single sign-on in environments where Kerberos v5 or other Single Sign
   On mechanisms may not be avaliable.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on August 31, 2017.

Copyright Notice

   Copyright (c) 2017 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents

Brown, et al.            Expires August 31, 2017                [Page 1]
Internet-Draft               LDAP SSO Token                February 2017

   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Requirements Language . . . . . . . . . . . . . . . . . . . .   3
   3.  Format  . . . . . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  SASL Component  . . . . . . . . . . . . . . . . . . . . . . .   3
     4.1.  Token formats . . . . . . . . . . . . . . . . . . . . . .   3
     4.2.  SASL Client . . . . . . . . . . . . . . . . . . . . . . .   5
     4.3.  SASL Authentication . . . . . . . . . . . . . . . . . . .   6
     4.4.  Valid Not Before Attribute  . . . . . . . . . . . . . . .   7
   5.  LDAP Component  . . . . . . . . . . . . . . . . . . . . . . .   7
     5.1.  Token Generation  . . . . . . . . . . . . . . . . . . . .   7
       5.1.1.  Token Generation Extended Operation . . . . . . . . .   8
     5.2.  Token Revocation  . . . . . . . . . . . . . . . . . . . .   8
       5.2.1.  Token Revocation Extended Operation . . . . . . . . .   9
     5.3.  Binding . . . . . . . . . . . . . . . . . . . . . . . . .   9
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   9
   7.  Requirements  . . . . . . . . . . . . . . . . . . . . . . . .   9
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   9
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   9
     8.2.  Informative References  . . . . . . . . . . . . . . . . .  10
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  10

1.  Introduction

   The need for new, simple single sign-on capable systems has arisen
   with the development of new technologies and systems.  For these
   systems we should be able to provide a simple, localised and complete
   single sign-on service.  This does not aim to replace Kerberos V5.
   It is designed for when Kerberos is too invasive for installation in
   an environment.

   Tokens generated by this system should be able to be transmitted over
   different protocols allowing middleware to relay tokens to clients.
   Clients can then contact the middleware natively and the middleware
   can negotiate the client authentication with the LDAP server.
Show full document text