Search results

Request for a multi-account Authorization Code flow that generates unique access tokens per account

Status: Open.

#251 In oauth-wg/oauth-v2-1;

· dfcoffin opened on May 13, 2026

Unclear on how Authorization Sever should accept request parameters

Status: Open.

#245 In oauth-wg/oauth-v2-1;

· ylemkimon opened on Apr 12, 2026

Consideration to forbid PKCE plain mode in OAuth 2.1

ietf-125

Status: Open.

#236 In oauth-wg/oauth-v2-1;

· corriganjeff opened on Jan 13, 2026

CORS Origin Validation for Token Endpoint

Status: Open.

#235 In oauth-wg/oauth-v2-1;

· tennantje opened on Dec 23, 2025

make mix-up mitigation via issuer mandatory

ietf-125

Status: Open.

#233 In oauth-wg/oauth-v2-1;

· will-bartlett opened on Nov 20, 2025

Protocol Flow Diagram

Status: Open.

#231 In oauth-wg/oauth-v2-1;

· jricher opened on Nov 4, 2025

Phishing/Audience Mix-Up Mitigation for Resources

Status: Open.

#215 In oauth-wg/oauth-v2-1;

· mcguinness opened on Jun 11, 2025

guidance on issues of using personal oauth flows for a service to get long term access and then refresh fails and then service does not have access

Status: Open.

#213 In oauth-wg/oauth-v2-1;

· dickhardt opened on May 14, 2025

guidance on rotating refreshing tokens and dealing with

Status: Open.

#212 In oauth-wg/oauth-v2-1;

· dickhardt opened on May 14, 2025

Reorganize section 7.1.1

Status: Open.

#200 In oauth-wg/oauth-v2-1;

· tlodderstedt opened on Dec 19, 2024

Reasons for recommending loopback redirects over private-use URI scheme

Status: Open.

#179 In oauth-wg/oauth-v2-1;

· archer-321 opened on May 19, 2024

Handling of colliding URI query parameter names

ietf-124

Status: Open.

#171 In oauth-wg/oauth-v2-1;

· SECtim opened on Feb 28, 2024

·  

version -13