OAuth 2.0 for Native Apps
draft-ietf-oauth-native-apps-09

Document Type Active Internet-Draft (oauth WG)
Last updated 2017-03-07 (latest revision 2017-03-06)
Replaces draft-wdenniss-oauth-native-apps
Stream IETF
Intended RFC status Best Current Practice
Formats plain text xml pdf html bibtex
Stream WG state Submitted to IESG for Publication Nov 2016
Document shepherd Hannes Tschofenig
Shepherd write-up Show (last changed 2017-03-07)
IESG IESG state Publication Requested
Consensus Boilerplate Yes
Telechat date
Responsible AD Kathleen Moriarty
Send notices to Hannes Tschofenig <Hannes.Tschofenig@gmx.net>
OAuth Working Group                                           W. Denniss
Internet-Draft                                                    Google
Intended status: Best Current Practice                        J. Bradley
Expires: September 7, 2017                                 Ping Identity
                                                           March 6, 2017

                       OAuth 2.0 for Native Apps
                    draft-ietf-oauth-native-apps-09

Abstract

   OAuth 2.0 authorization requests from native apps should only be made
   through external user-agents, primarily the user's browser.  This
   specification details the security and usability reasons why this is
   the case, and how native apps and authorization servers can implement
   this best practice.

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 September 7, 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
   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

Denniss & Bradley       Expires September 7, 2017               [Page 1]
Internet-Draft          OAuth 2.0 for Native Apps             March 2017

   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.  Overview  . . . . . . . . . . . . . . . . . . . . . . . . . .   4
     4.1.  Authorization Flow for Native Apps Using the Browser  . .   5
   5.  Using Inter-app URI Communication for OAuth . . . . . . . . .   6
   6.  Initiating the Authorization Request from a Native App  . . .   6
   7.  Receiving the Authorization Response in a Native App  . . . .   7
     7.1.  App-declared Custom URI Scheme Redirection  . . . . . . .   7
     7.2.  App-claimed HTTPS URI Redirection . . . . . . . . . . . .   8
     7.3.  Loopback URI Redirection  . . . . . . . . . . . . . . . .   9
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .   9
     8.1.  Embedded User-Agents  . . . . . . . . . . . . . . . . . .   9
     8.2.  Non-Browser External User-Agents  . . . . . . . . . . . .  10
     8.3.  Phishability of In-App Browser Tabs . . . . . . . . . . .  10
     8.4.  Protecting the Authorization Code . . . . . . . . . . . .  11
     8.5.  OAuth Implicit Flow . . . . . . . . . . . . . . . . . . .  12
     8.6.  Loopback Redirect Considerations  . . . . . . . . . . . .  12
     8.7.  Registration of Native App Clients  . . . . . . . . . . .  12
     8.8.  Client Authentication . . . . . . . . . . . . . . . . . .  13
     8.9.  Client Impersonation  . . . . . . . . . . . . . . . . . .  13
     8.10. Cross-App Request Forgery Protections . . . . . . . . . .  14
     8.11. Authorization Server Mix-Up Mitigation  . . . . . . . . .  14
   9.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  14
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .  15
     10.1.  Normative References . . . . . . . . . . . . . . . . . .  15
     10.2.  Informative References . . . . . . . . . . . . . . . . .  15
   Appendix A.  Server Support Checklist . . . . . . . . . . . . . .  16
   Appendix B.  Operating System Specific Implementation Details . .  16
     B.1.  iOS Implementation Details  . . . . . . . . . . . . . . .  17
     B.2.  Android Implementation Details  . . . . . . . . . . . . .  17
     B.3.  Windows Implementation Details  . . . . . . . . . . . . .  18
     B.4.  macOS Implementation Details  . . . . . . . . . . . . . .  18
     B.5.  Linux Implementation Details  . . . . . . . . . . . . . .  19
Show full document text