Skip to content

Align /token responses with RFC 6749 cache and Basic encoding #272

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
oej merged 2 commits into from
Sep 17, 2026
Merged

Align /token responses with RFC 6749 cache and Basic encoding #272

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
5c32c32
Align /token responses with RFC 6749 cache and Basic encoding rules.
Mehrn0ush Sep 11, 2026
9987cd2
Drop Pragma from token responses
Mehrn0ush Sep 13, 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
6 changes: 5 additions & 1 deletion spec/openapi.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2464,7 +2464,11 @@ components:
description: |
API key credentials, presented to `/token` only: the API key identifier as the
user-id and the API key secret as the password (RFC 7617, RFC 6749 section
2.3.1). Servers shall not accept API key credentials directly on other TEA
2.3.1). Per RFC 6749 section 2.3.1, the identifier and secret are each encoded as
`application/x-www-form-urlencoded` before they are joined with a colon and
Base64-encoded for the `Authorization` header. Clients and servers shall apply
that encoding so credentials containing `:`, `@`, or other reserved characters
interoperate. Servers shall not accept API key credentials directly on other TEA
endpoints; clients shall exchange them for an access token first.
security:
- bearerAuth: []
Expand Down