This repository was archived by the owner on Dec 18, 2024. It is now read-only.
[Snyk] Upgrade @inrupt/solid-client-authn-browser from 2.0.0 to 2.2.6 #1021
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.
Snyk has created this PR to upgrade @inrupt/solid-client-authn-browser from 2.0.0 to 2.2.6.
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.
The recommended version is 8 versions ahead of your current version.
The recommended version was released on 2 months ago.
Release notes
Package name: @inrupt/solid-client-authn-browser
-
2.2.6 - 2024-09-18
- Repository URL in
-
2.2.5 - 2024-09-16
- Node 22 is now supported
-
2.2.4 - 2024-06-24
- The
- The
-
2.2.3 - 2024-06-20
- Fix parsing
-
2.2.2 - 2024-06-18
- Maintain token type in
-
2.2.1 - 2024-06-05
- Fix #3518: Prevent refresh token from being persisted in local storage.
- @ garciafdezpatricia made their first contribution in #3498
-
2.2.0 - 2024-05-03
- It is now possible to prevent a
-
2.1.0 - 2024-03-14
- OpenID Providers with multiple JWK in their JWKS are now supported. Thanks to
- Authorization code flow for statically registered clients is now supported. Statically registered
- Fix non-DPoP bound tokens support in browser: a bug in the handling of non-DPoP-bound tokens was
-
2.0.0 - 2023-12-20
- Node 16 is no longer supported. The global
- The
- the
- The
- The
- The UMD build of
- Moved from
from @inrupt/solid-client-authn-browser GitHub release notesnode and browser
package.jsonupdated to set therepository.typeproperty togit. This intends atrestoring the previous behavior of
npm view @ inrupt/solid-client-authn repository.url, expected to returngit+https://github.com/inrupt/solid-client-authn-js.git.Full Changelog: v2.2.5...v2.2.6
New Features
Full Changelog: v2.2.4...v2.2.5
Bugfixes
node and browser
clientAppIdproperty is now correctly set in theISessionInfoobjects returned by thehandleIncomingRedirectfunction inClientAuthenticationand in theSessionclass.node
keepAliveoption (introduced in v2.2.0) is now correctly observed in a script using the Client Credentials flow (i.e. using aclientIdand aclientSecretto log in). It previously was disregarded, and theSessionalways self-refreshed in the backgroundFull Changelog: v2.2.3...v2.2.4
Bugfix
node and browser
clientIdfrom ID Tokenazpclaim: the parsing of the ID Token payload was not correctly extracting theclientIdfrom theazpclaim. As a result,session.info.clientAppIdwas not being initialised upon successful login, which prevented theidplogout of the session from working as expected.Full Changelog: v2.2.2...v2.2.3
Bugfix
node
getSessionIdFromStorage: When loading a session from storage on the server(using
getSessionIdFromStorage), the token type (i.e. DPoP-bound or not, referred to as Bearer) isnow consistent with the token type initially associated with the session. Previously, regardless of
the token type requested when logging the session in, the token type defaulted to
DPoPwhen loggingthe session back in on load from storage, causing authentication issues.
Full Changelog: v2.2.1...v2.2.2
Bugfix
browser
New Contributors
Full Changelog: v2.2.0...v2.2.1
New Feature
node
Sessionself-refreshing in NodeJS. To do so, a newparameter is added to the constructor:
Session({ keepAlive: false }). This preventsthe
Sessionsetting a callback to refresh the Access Token before it expires, whichcould cause a memory leak in the case of a server-side application with many users.
It also avoids unnecessary requests being sent to the OpenID Provider.
New Feature
node and browser
@ pavol-brunclik-compote for the original contribution.
node
clients previously defaulted to the Client Credentials flow, it is no longer an assumption.
Bugfix
browser
preventing the auth code grant to complete, with a 401 to the OpenId Provider Token Endpoint
observed on redirect after the user authenticated. It is now possible to do
session.login({/*...*/, tokenType: "Bearer"})and get a successful result.Breaking Changes
fetchfunction is used instead of@ inrupt/universal-fetch.This means this library now only works with Node 18 and higher.
Sessionclass no longer extendsEventEmitter. Instead, it exposes aneventsattribute implementingEventEmitter. We do not recommend to useSessioninstance'seventsattribute as an arbitrary events emitter,and encourage users to only use the supported events and documented API.
SessionmethodsonLogin,onLogout,onError,onSessionRestore,onSessionExpirationandonNewRefreshTokenhave been removed. They are replaced by calls to
session.events.on, using the appropriate event name.Sessionconstructor changes:onNewRefreshTokenparameter is no longer supported. Its usage is replaced by callingsession.events.onusing the
EVENTS.NEW_REFRESH_TOKENconstant as a first parameter, and a callback handling the token as asecond parameter.
useEssSessionparameter is no longer supported.getClientAuthenticationWithDependenciesis no longer exported as part of the public API, and is now internal-only.@ inrupt/oidc-client-extis no longer available. Since this is a package only intended to beconsumed by
@ inrupt/solid-client-authn-browser, which doesn't have a UMD build, this change should have noimpact.
Build system changes
rollup-plugin-typescript2to@ rollup/plugin-typescript. Although this should not be a breaking change,upgrading may require extra attention.
Important
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information: