Skip to content

Implementation Advice: JARM downgrade - #876

Open
davetonge-mh wants to merge 1 commit into
davetonge/impl-advice/197-org-certificatesfrom
davetonge/impl-advice/733-jarm-downgrade
Open

davetonge-mh wants to merge 1 commit into
davetonge/impl-advice/197-org-certificatesfrom
davetonge/impl-advice/733-jarm-downgrade

Conversation

@davetonge-mh

@davetonge-mh davetonge-mh commented Oct 28, 2026 •

Copy link
Copy Markdown
Contributor

A client that requests JARM from an authorization server that advertises JARM support should reject an authorization response whose parameters, such as code and state, arrive directly instead of in a response JWT. JARM's processing rules only cover validating a JWT response, so they do not address this case. Based on the text proposed on the issue, reworded to say what a non-JARM response is. The JARM reference is copied from Message Signing.

Closes #733

github-actions Bot pushed a commit that referenced this pull request Oct 28, 2026
@github-actions

github-actions Bot commented Oct 28, 2026 •

Copy link
Copy Markdown

📄 HTML preview

Drafts changed in this PR:

All drafts

Preview of cb93fa2; updated on every push. For review only — the official specifications are published at https://openid.net/specs/

Based on the text Nat asked for on #733, but says what the downgrade
looks like: the response parameters arrive directly instead of in a
response JWT. The JARM reference is copied from Message Signing.

Refs #733
@davetonge-mh
davetonge-mh force-pushed the davetonge/impl-advice/733-jarm-downgrade branch from d94cf24 to cb93fa2 Compare October 28, 2026 13:58
github-actions Bot pushed a commit that referenced this pull request Oct 28, 2026

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant