DRD26-J. For OAuth, use a secure Android method to deliver access tokens

This rule was developed in part by Rachel Xu and Zifei (FeiFei) Han at the October 20-22, 2017 OurCS Workshop ( http://www.cs.cmu.edu/ourcs/register.html ).
For more information about this statement, see the About the OurCS Workshop page.

For OAuth, use a secure Android method to deliver access tokens. The method to do with mobile apps and their platforms is not specified in the OAuth 1.0 or OAuth 2.0 standards. Access tokens can be securely delivered if the service provider can identify recipients using a globally unique identifier.

Under Construction

This guideline is under construction.

Noncompliant Code Example

This noncompliant code example shows an application that

TBD

An Intent can securely send an access token to its intended mobile relying party app, using an explicit intent, because the relying party can be uniquely identified through its developer key hash.

Compliant Solution

In this compliant solution the application

TBD

Risk Assessment

Automated Detection

Tool

Version

Checker

Description

Related Vulnerabilities

Hyperlink black-font text "the CERT website" below, with URL as follows: >

In the URL example above, <RULE_ID> should be substituted by this CERT guideline ID (e.g., INT31-C). Then, remove this purple-font paragraph.

Search for vulnerabilities resulting from the violation of this rule on the CERT website.

Related Guidelines

Fill in the table below with at least one entry row, per these instructions , then remove this purple-font section.

Bibliography