Skip to content

Implementation Advice: JARM downgrade #876

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

Open
davetonge-mh wants to merge 1 commit into
base: davetonge/impl-advice/197-org-certificates
Choose a base branch
from
Open

Implementation Advice: JARM downgrade #876

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
17 changes: 17 additions & 0 deletions FAPI_2_0_Implementation_Advice.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -197,6 +197,10 @@ Some ecosystems issue certificates to organizations rather than to individual cl

NOTE: One way to distinguish a client from the organization that operates it is for each client to register the certificates and keys it uses: the subject distinguished name of its TLS client certificate using the `tls_client_auth_subject_dn` client metadata parameter [@RFC8705], and its signing keys at a `jwks_uri` [@RFC7591].

## JARM Downgrade

A client should reject the response if it requests a JARM [@JARM] response from an authorization server that advertises JARM support in its `response_modes_supported` metadata but receives the authorization response parameters, such as `code` and `state`, directly instead of in a `response` JWT.

## Access Token Size Considerations

As key size grows and more elements are added to access tokens, it's possible for the HTTP Authorization header containing the access token plus other headers to cumulatively be larger than the allowed buffer size for HTTP requests in many web infrastructure components. It is important to watch this closely via logging and alerting to ensure that production traffic is not adversely affected and that adjustments to the allowed buffer size can be made in a timely manner.
Expand Down Expand Up @@ -323,6 +327,19 @@ This document was developed by the OpenID FAPI Working Group.
</front>
</reference>

<reference anchor="JARM" target="https://openid.net/specs/oauth-v2-jarm-final.html">
<front>
<title>JWT Secured Authorization Response Mode for OAuth 2.0 (JARM)</title>
<author initials="T." surname="Lodderstedt" fullname="Torsten Lodderstedt">
<organization>Yes</organization>
</author>
<author initials="B." surname="Campbell" fullname="Brian Campbell">
<organization>Ping</organization>
</author>
<date day="9" month="Nov" year="2022"/>
</front>
</reference>

<reference anchor="NIST.SP.800-57pt1r5" target="https://csrc.nist.gov/publications/detail/sp/800-57-part-1/rev-5/final">
<front>
<title>Recommendation for Key Management: Part 1 – General</title>
Expand Down
Loading