feat: Add support for Pushed Authorization Requests (PAR)#321
Open
An0n-01 wants to merge 3 commits intofastify:mainfrom
Open
feat: Add support for Pushed Authorization Requests (PAR)#321An0n-01 wants to merge 3 commits intofastify:mainfrom
An0n-01 wants to merge 3 commits intofastify:mainfrom
Conversation
Implements support for Pushed Authorization Requests (PAR) according to RFC9126. This enhances security by allowing clients to push authorization request parameters directly to the authorization server via a backchannel POST request, receiving a request_uri to use in the subsequent authorization request. Prevents parameter tampering and reduces exposure in browser URLs.
An0n-01
changed the title
mcollina
requested changes
Feb 16, 2026
Member
mcollina
left a comment
mcollina
left a comment
There was a problem hiding this comment.
can you add some more tests for the full flow?
| if (v !== undefined && v !== null) { | ||
| body.append(k, Array.isArray(v) ? v.join(' ') : String(v)) | ||
| } | ||
| }) |
| res.on('data', (chunk) => { rawData += chunk }) | ||
| res.on('end', () => { | ||
| try { | ||
| const data = JSON.parse(rawData) |
Member
There was a problem hiding this comment.
Can you use secure-json-parse here?
|
|
||
| function onParResponse (res) { | ||
| let rawData = '' | ||
| res.on('data', (chunk) => { rawData += chunk }) |
Member
There was a problem hiding this comment.
you need to set the encoding correctly
| if (res.statusCode >= 200 && res.statusCode < 300) { | ||
| callback(null, data) | ||
| } else { | ||
| const err = new Error(`PAR request failed: ${data.error_description || data.error || 'Unknown error'}`) |
| } | ||
|
|
||
| function errHandler (e) { | ||
| const err = new Error('Problem calling PAR endpoint. See innerError for details.') |
|
|
||
| // Validate that PAR endpoint was discovered | ||
| if (!authFromMetadata.parPath) { | ||
| next(new Error('PAR is enabled but pushed_authorization_request_endpoint was not found in discovery metadata')) |
Author
|
I'll look at everything asap |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hey.
I've implemented #320 now. I've also tested with my local keycloak instance and it works.
Implemented support for Pushed Authorization Requests (PAR) according to RFC9126.
This enhances security by allowing clients to push authorization request parameters directly to the authorization server via a backchannel POST request, receiving a request_uri to use in the subsequent authorization request.
Prevents parameter tampering and reduces exposure in browser URLs.
Checklist
npm run test && npm run benchmark --if-presentand the Code of conduct