Skip to content

Update 'response_type' requirements in documentation #170

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
aaronpk merged 2 commits into from
Feb 27, 2026
Merged

Update 'response_type' requirements in documentation #170

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
36fc427
Update 'response_type' requirements in documentation
gffletch Feb 27, 2026
6627baf
Apply suggestion from @aaronpk
aaronpk Feb 27, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions draft-ietf-oauth-first-party-apps.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -279,6 +279,9 @@ format with a character encoding of UTF-8 in the HTTP request body:
: OPTIONAL. The code challenge method as defined by {{RFC7636}}.
See {{redirect-to-web}} for details.

"response_type":
: REQUIRED. Per section 3.1.1 of {{RFC6749}} `response_type` is required and for this specification MUST contain the value of `code`.

Specific implementations as well as extensions to this specification MAY define additional parameters to be used at this endpoint.

For example, the client makes the following request to initiate a flow
Expand Down