Skip to content

Comments

chore(deps): update dependency oidc-provider to v9#15

Open
renovate[bot] wants to merge 1 commit intomainfrom
renovate/oidc-provider-9.x
Open

chore(deps): update dependency oidc-provider to v9#15
renovate[bot] wants to merge 1 commit intomainfrom
renovate/oidc-provider-9.x

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Jun 14, 2025

This PR contains the following updates:

Package Change Age Confidence
oidc-provider 8.8.19.6.1 age confidence
@types/oidc-provider (source) 8.8.19.5.0 age confidence

Release Notes

panva/node-oidc-provider (oidc-provider)

v9.6.1

Compare Source

Refactor
  • extract NON_REJECTABLE_CLAIMS into shared constant (2b7c025)
  • extract shared grant handler helpers to reduce duplication (f5eee9e)
  • extract shared token finder for introspection and revocation (666c2b0)
Fixes
  • required PAR should not affect CIBA and DAG (8167bd0)

v9.6.0

Compare Source

Features
Documentation

v9.5.2

Compare Source

Refactor

v9.5.1

Compare Source

Fixes
  • safeguard global navigator access (1caae21)

v9.5.0

Compare Source

Features
  • support ML-DSA JWS algorithm identifiers (f308b09)
Refactor
  • add a warning for more unsupported runtimes (c55d58e)
  • make warn/info warnings colorization a no-op in nonTTY (0c0a5b6)

v9.4.2

Compare Source

Fixes
  • check for native logout redirect allowed same way as during auth (419f286), closes #​1351

v9.4.1

Compare Source

Documentation
  • add an getAttestationSignaturePublicKey example (3a7730c)
Refactor
  • avoid code generation from strings by pre-compiling eta views (f997073)
  • drop the default implementation of pairwiseIdentifier (6a2338a)
  • remove oidc-token-hash dependency (b607491)

v9.4.0

Compare Source

Features
  • Experimental support for Attestation-Based Client Authentication (d655ebd)
Refactor
  • consistently lowercase header names and use req/res aliases (1748a54)
  • cors: update default client-based cors helper (77e06eb)
  • reconcile dpop and attestation challenge implementations (e31f639)
Documentation
  • updated documentation for configuration options (5710d61)

v9.3.0

Compare Source

Features
  • revocation: add an allowed token revocation policy helper (a7e47e4)
Documentation
Fixes
  • introspection: use unsupported_token_type to indicate structured jwt tokens cannot be introspected (c9001be)
  • revocation: use unsupported_token_type to indicate structured jwt tokens cannot be revoked (b45b00c)
Refactor
  • pull structured token rejection to a shared middleware (30367af)

v9.2.0

Compare Source

Features
  • expose RFC8414 Authorization Server Metadata route (c5bd90f)

v9.1.3

Compare Source

Fixes
  • ensure an account's accountId and claims().sub is the same (9b89153), closes #​1336

v9.1.2

Compare Source

Fixes
  • ignore allowOmittingSingleRegisteredRedirectUri when FAPI 2.0 is used (e2de529)

v9.1.1

Compare Source

Refactor
  • oidc-provider now uses koa@​3 (3a83d32)

v9.1.0

Compare Source

Features
  • experimental support for OIDC RP Metadata Choices (f3550da)
Fixes
  • only include DPoP-Nonce in Access-Control-Expose-Headers when DPoP is enabled (e769aa8)
Refactor
  • avoid assignment operators in conditional expressions (b7ed877)
  • improve static find performance (106f94a)
  • update some default helpers for readability (0818c36)
Documentation
  • more clarity for features.dPoP.allowReplay (779a141)

v9.0.1

Compare Source

Documentation
  • mark experimental features more distinctly (986adc5)
  • update references and styling of spec links (a4787b8)
Fixes
  • DCR endpoints only include www-authenticate for non-registration related errors (9a864d6)
Refactor
  • client schema defaults and static props (843943d)
  • handle frame-ancestors in wmrm without a regexp (4f85585)
  • push multiple elements to the recognized array in client_schema (d478a8b)
  • simpler DCR validate registration access token (5f01eda)

v9.0.0

Compare Source

⚠ BREAKING CHANGES
  • authorization and logout endpoints no longer support the HTTP POST method by default, this can be re-enabled using the enableHttpPostMethods boolean configuration, this also requires that cookies.long.sameSite is set to none
  • cookie session sameSite attribute default is now "lax" instead of "none"
  • userinfo requests with bearer tokens will now fail if they also include DPoP
  • userinfo now includes both dpop and bearer challenges when dpop is enabled
  • accessing protected resources without an access token will now yield a 401 HTTP Status Code instead of a 400
  • default PKCE configuration no longer requires PKCE to be used unless RFC9700 or a given profile says so
  • removed the provider.Account getter
  • 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
  • the Provider no longer includes a catch-all 404 Not Found error handler
  • FAPI profile behaviours no longer force PKCE, these should be forced by configuring the pkce.required configuration helper the default of which already does so.
  • the server's JWK Key IDs (JWK kid parameter) now must be unique, no two keys must use the same kid.
  • the revokeGrantPolicy configuration helper is now also invoked during opaque Access Token revocation, its default return remains false for this case though
  • 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
  • authorization code grant type issued ID Tokens no longer include at_hash
  • device authorization grant type issued ID Tokens no longer include at_hash
  • refresh token grant type issued ID Tokens no longer include at_hash
  • implicit grant type issued ID Tokens no longer include s_hash unless the request is a FAPI 1.0 Final request
  • global fetch() API is now used to make outgoing HTTP requests instead of the "got" module.
  • 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.
  • Enabling JAR (Request Objects by Value) is now enabled via features.requestObjects.enabled boolean instead of features.requestObjects.request boolean
  • removed support for Passing a Request Object by Reference (JAR request_uri)
  • removed legacy sameSite cookie fallback
  • removed support for Node.js 18.x
  • removed support for Node.js 20.x
  • removed the pkce.methods configuration
  • removed the features.requestObjects.mode configuration
  • removed support for Ed448
  • removed support for X448
  • removed support for secp256k1 / ES256K
  • removed support for FAPI 1.0 ID2
Features
  • Access Token revocation may now also optionally revoke the underlying grant (4f69668)
  • add support for the fully-specified Ed25519 JWS Algorithm Identifier (645b900)
  • DPoP support is now enabled by default (a5694af)
  • Experimental support for external signing keys, e.g. in a KMS or HSM (8b3ceff)
  • expose current requests' ctx via Provider.ctx static getter (1fbd81b)
  • update FAPI 2.0 implementation to FAPI 2.0 Final (eff3115)
Documentation
  • auto-format code blocks (c2c520f)
  • dpop cannot acked anymore, it is stable (a48c51f)
  • improvements to linked resources (cf77770)
  • mention external types (5f8a450)
  • move adapters to the Community Guides Discussions section (ba806ca)
  • move recipes to the Community Guides Discussions section (cd8da28)
  • remove mentions of the connect server framework (7cb1aaa)
  • update README to use named exports (8355886)
  • update version support matrix (abbfe2f)
Fixes
  • no access token provided error is now a 401 (8493e2d)
  • userinfo now includes both dpop and bearer challenges when dpop is enabled (1093f6b)
Refactor
  • change default PKCE usage requirement (fdf8ad8)
  • change default session cookie from sameSite none to lax (b47eee8)
  • cleanup unused azp claim code (6c57e63)
  • deprecate the .app getter (9b61212)
  • disable HTTP POST Method handling of authorization and logout endpoints (d56304c)
  • encryption and key derivation is not blocking the main thread (73a422f)
  • ensure all route handlers are final (8cc44e6)
  • escape www-authenticate backslashes despite not directly using them (e789b98)
  • increase all random identifiers from ~126 bits of randomness to ~256 (45721f8)
  • minimal change to support koa@​3 (925cee5)
  • no more warnings if cookie keys are missing (7ab6157)
  • omit generic "typ: JWT" in issued JSON Web Tokens (4eb4004)
  • pass over internal configuration getters (0243964)
  • Provider is now the Koa application instance (167216e)
  • remove hardcoded require PKCE checks (be0b2fd)
  • remove object-hash dependency (fda9385)
  • remove optional ID Token _hash claims (58ca2c2)
  • remove the provider.Account getter (dd2bde4)
  • remove unused code (e5fc3cb)
  • remove uses of randomFill and Buffer.allocUnsafe (00fe106)
  • removed legacy sameSite cookie fallback (2defa70)
  • removed support for FAPI 1.0 ID2 (311e3e2)
  • removed support for Passing a Request Object by Reference (JAR request_uri) (bacf375)
  • removed the features.requestObjects.mode configuration (4ec8327)
  • removed the pkce.methods configuration (4a736b8)
  • Request Object (JAR) is now enabled with features.requestObjects.enabled (20d60a4)
  • simplify default assertJwtClaimsAndHeader configuration (1ea27a6)
  • update Node.js support matrix (db57556)
  • use fetch() api to make outgoing HTTP requests (cc70e5a)
  • use hkdf in dpop's rolling nonce calculation (7b77967)
  • use more optional chaining (e5539ae)
  • use oneshot hash methods instead of intermediate Hash objects (2dc4bd1)
  • use structuredClone instead of JSON.stringify then parse (ad02170)
  • use URL.parse (11e1b33)
  • userinfo requests with bearer tokens will now fail if they also include DPoP (e5efa5c)

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/oidc-provider-9.x branch 2 times, most recently from c19f7a7 to bba63a4 Compare June 19, 2025 20:02
@renovate renovate bot force-pushed the renovate/oidc-provider-9.x branch 2 times, most recently from d10e2dd to bee1212 Compare June 25, 2025 23:03
@renovate renovate bot force-pushed the renovate/oidc-provider-9.x branch 7 times, most recently from cf9256d to b129f78 Compare July 22, 2025 17:15
@renovate renovate bot force-pushed the renovate/oidc-provider-9.x branch 2 times, most recently from ed35a74 to f71a283 Compare August 4, 2025 15:22
@renovate renovate bot force-pushed the renovate/oidc-provider-9.x branch 2 times, most recently from 8ae9615 to f49276a Compare August 13, 2025 16:56
@renovate renovate bot force-pushed the renovate/oidc-provider-9.x branch 2 times, most recently from 3be82dc to dd8a5ab Compare August 23, 2025 08:55
@renovate renovate bot force-pushed the renovate/oidc-provider-9.x branch 4 times, most recently from 90a4c17 to 89b1b30 Compare September 7, 2025 01:52
@renovate renovate bot force-pushed the renovate/oidc-provider-9.x branch 2 times, most recently from fa16548 to 9dc97d4 Compare September 14, 2025 00:36
@renovate renovate bot force-pushed the renovate/oidc-provider-9.x branch 2 times, most recently from 1d5abfd to f9478b8 Compare September 22, 2025 04:24
@renovate renovate bot force-pushed the renovate/oidc-provider-9.x branch from f9478b8 to 88c9b7a Compare September 25, 2025 17:01
@renovate renovate bot force-pushed the renovate/oidc-provider-9.x branch 2 times, most recently from 54cad86 to 3cd9c80 Compare October 7, 2025 20:05
@renovate renovate bot force-pushed the renovate/oidc-provider-9.x branch 2 times, most recently from f38a9ad to 4d0853f Compare October 23, 2025 16:48
@renovate renovate bot force-pushed the renovate/oidc-provider-9.x branch 2 times, most recently from 2314e9c to 2354d31 Compare October 29, 2025 00:42
@renovate renovate bot force-pushed the renovate/oidc-provider-9.x branch 2 times, most recently from ae2919c to 8e0994b Compare November 3, 2025 22:56
@renovate renovate bot force-pushed the renovate/oidc-provider-9.x branch 2 times, most recently from 71c8e5b to 0fa0d45 Compare November 17, 2025 04:55
@renovate renovate bot force-pushed the renovate/oidc-provider-9.x branch from 0fa0d45 to afc9014 Compare November 18, 2025 11:53
@renovate renovate bot force-pushed the renovate/oidc-provider-9.x branch 3 times, most recently from c13a06b to fd18554 Compare December 8, 2025 06:07
@renovate renovate bot force-pushed the renovate/oidc-provider-9.x branch from fd18554 to 800f705 Compare December 22, 2025 04:44
@renovate renovate bot force-pushed the renovate/oidc-provider-9.x branch 2 times, most recently from 196987c to bfc5a63 Compare January 5, 2026 06:43
@renovate renovate bot force-pushed the renovate/oidc-provider-9.x branch 3 times, most recently from 8148dfc to d9da972 Compare January 15, 2026 17:48
@renovate renovate bot force-pushed the renovate/oidc-provider-9.x branch 3 times, most recently from e8d29cd to 93940ae Compare January 26, 2026 04:38
@renovate renovate bot force-pushed the renovate/oidc-provider-9.x branch from 93940ae to b21ef52 Compare February 2, 2026 06:07
@renovate renovate bot force-pushed the renovate/oidc-provider-9.x branch 2 times, most recently from 3e34f2b to 0110334 Compare February 17, 2026 18:39
@renovate renovate bot force-pushed the renovate/oidc-provider-9.x branch from 0110334 to 9946e9e Compare February 19, 2026 09:01
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.

0 participants