Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Authentication Indicator in Kerberos Tickets (RFC8129)

IP.com Disclosure Number: IPCOM000249706D
Original Publication Date: 2017-Mar-01
Included in the Prior Art Database: 2017-Mar-23
Document File: 12 page(s) / 11K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

A. Jain: AUTHOR [+3]

Abstract

Kerberos [RFC4120] allows secure interaction among users and services over a network. It supports a variety of authentication mechanisms using its pre-authentication framework [RFC6113]. The Kerberos authentication service has been architected to support password-based authentication as well as multi-factor authentication using one-time password devices, public-key cryptography, and other pre-authentication schemes. Implementations that offer pre-authentication mechanisms supporting significantly different strengths of client authentication may choose to keep track of the strength of the authentication that was used, for use as an input into policy decisions.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 24% of the total text.

Internet Engineering Task Force (IETF)                           A. Jain Request for Comments: 8129                                  Georgia Tech Updates: 4120                                                  N. Kinder Category: Standards Track                                    N. McCallum ISSN: 2070-1721                                            Red Hat, Inc.                                                               March 2017

               Authentication Indicator in Kerberos Tickets

Abstract

   This document updates RFC 4120, as it specifies an extension in the    Kerberos protocol.  It defines a new authorization data type,    AD-AUTHENTICATION-INDICATOR.  The purpose of introducing this data    type is to include an indicator of the strength of a client's    authentication in service tickets so that application services can    use it as an input into policy decisions.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force    (IETF).  It represents the consensus of the IETF community.  It has    received public review and has been approved for publication by the    Internet Engineering Steering Group (IESG).  Further information on    Internet Standards is available in Section 2 of RFC 7841.

   Information about the current status of this document, any errata,    and how to provide feedback on it may be obtained at    http://www.rfc-editor.org/info/rfc8129.

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    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.

 Jain, et al.                 Standards Track                    [Page 1]
 RFC 8129                Authentication Indicator              March 2017

 Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2    2.  Document Conventions  . . . . . . . . . . . . . . . . . . . .   2    3.  AD Type Specification . . . . . . . . . . . . . . . . . . . .   2    4.  Assigned...