OAuth 2.0 Device Posture Signals

Document Type Expired Internet-Draft (individual)
Last updated 2018-05-17 (latest revision 2017-11-13)
Stream (None)
Intended RFC status (None)
Expired & archived
plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


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.


William Denniss (wdenniss@google.com)
Karl McGuinness (kmcguinness@okta.com)
John Bradley (ietf@ve7jtb.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)