-
-
Notifications
You must be signed in to change notification settings - Fork 789
v9.0.0-rc.1 #1318
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.
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
Closed
Closed
v9.0.0-rc.1 #1318
Conversation
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
BREAKING CHANGE: removed support for Ed448 BREAKING CHANGE: removed support for X448 BREAKING CHANGE: removed support for secp256k1 / ES256K
BREAKING CHANGE: removed support for Node.js 18.x BREAKING CHANGE: removed support for Node.js 20.x
…(JAR request_uri)
…bjects.enabled BREAKING CHANGE: Enabling JAR (Request Objects by Value) is now enabled via features.requestObjects.enabled boolean instead of features.requestObjects.request boolean
BREAKING CHANGE: global fetch() API is now used to make outgoing HTTP requests instead of the "got" module. BREAKING CHANGE: the httpOptions configuration option was removed and a new option to accomodate the use of fetch() interface was added. This options is aptly called "fetch" and its call signature and expected returns mirror the fetch() API.
BREAKING CHANGE: CIBA ping and poll delivery mode ID Tokens no longer include at_hash, urn:openid:params:jwt:claim:rt_hash, and urn:openid:params:jwt:claim:auth_req_id BREAKING CHANGE: authorization code grant type issued ID Tokens no longer include at_hash BREAKING CHANGE: device authorization grant type issued ID Tokens no longer include at_hash BREAKING CHANGE: refresh token grant type issued ID Tokens no longer include at_hash BREAKING CHANGE: implicit grant type issued ID Tokens no longer include s_hash unless the request is a FAPI 1.0 Final request
…erlying grant BREAKING CHANGE: the revokeGrantPolicy configuration helper is now also invoked during opaque Access Token revocation, its default return remains false for this case though
…r HSM BREAKING CHANGE: the server's JWK Key IDs (JWK kid parameter) now must be unique, no two keys must use the same kid.
BREAKING CHANGE: the Provider no longer includes a catch-all 404 Not Found error handler
BREAKING CHANGE: all Provider routes will now end the HTTP request when finished, koa middlewares that are "downstream" will no longer be executed after a route is matched in oidc-provider, "upstream" control flows are unaffected
BREAKING CHANGE: removed the provider.Account getter
BREAKING CHANGE: default PKCE configuration no longer requires PKCE to be used unless RFC9700 or a given profile says so
Repository owner
locked and limited conversation to collaborators
Apr 2, 2025
Owner
Author
|
Superseded by v9.0.0-rc.2 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
v9.0.0-rc.1
⚠ BREAKING CHANGES
Features
Documentation
Refactor
.appgetter (f2fc768)