OAuth 2.0 Device Posture Signals
draft-wdenniss-oauth-device-posture-01

Document Type Active Internet-Draft (individual)
Last updated 2017-11-13
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)
OAuth Working Group                                           W. Denniss
Internet-Draft                                                    Google
Intended status: Standards Track                          KM. McGuinness
Expires: May 17, 2018                                               Okta
                                                              J. Bradley
                                                                  Yubico
                                                       November 13, 2017

                    OAuth 2.0 Device Posture Signals
                 draft-wdenniss-oauth-device-posture-01

Abstract

   Enterprise and security focused OAuth providers typically want
   additional signals to confirm user presence when users return to
   previously authorized apps.  Rather than requiring a full
   reauthentication, or require enrollment in a mobile device management
   solution, some authorization servers may be willing to accept device
   posture signals from the app, like the fact that device has a lock
   screen, as confirmation of user presence.  This document details how
   OAuth native app clients can communicate device posture signals to
   OAuth providers.

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 https://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 May 17, 2018.

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

Denniss, et al.           Expires May 17, 2018                  [Page 1]
Internet-Draft      OAuth 2.0 Device Posture Signals       November 2017

   (https://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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Notational Conventions  . . . . . . . . . . . . . . . . . . .   3
   3.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  Device Posture Signal Dictionary  . . . . . . . . . . . . . .   3
   5.  Authorization Request Device Posture Hint . . . . . . . . . .   5
   6.  Token Endpoint Device Posture Enforcement . . . . . . . . . .   5
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   6
     7.1.  Device Posture Scope  . . . . . . . . . . . . . . . . . .   6
     7.2.  Spoofed Devices . . . . . . . . . . . . . . . . . . . . .   6
     7.3.  App Trustworthiness . . . . . . . . . . . . . . . . . . .   6
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   7
     8.1.  OAuth Parameters Registration . . . . . . . . . . . . . .   7
       8.1.1.  Registry Contents . . . . . . . . . . . . . . . . . .   7
     8.2.  OAuth Extensions Error Registration . . . . . . . . . . .   7
       8.2.1.  Registry Contents . . . . . . . . . . . . . . . . . .   7
     8.3.  Device Posture Keys Registry  . . . . . . . . . . . . . .   7
       8.3.1.  Registration Template . . . . . . . . . . . . . . . .   8
       8.3.2.  Initial Registry Contents . . . . . . . . . . . . . .   9
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  10
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .  10
     9.2.  Informative References  . . . . . . . . . . . . . . . . .  11
   Appendix A.  Acknowledgements . . . . . . . . . . . . . . . . . .  11
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  11

1.  Introduction

   Users who follow strong security practices on their devices - such as
   configuring screen locks, and not enabling admin privileges (commonly
   known as "rooting" or "jailbreaking") - shouldn't need to
   reauthenticate frequently to the individual apps on their device.

   This specification details how apps can send device posture signals
   to the OAuth Token Endpoint, enabling it to enforce device policy
   compliance, and avoid the need for reauthentication in some cases.

   It is designed to provide a mechanism for honest apps to communicate
Show full document text