[Snyk] Upgrade @inrupt/solid-client-authn-browser from 2.0.0 to 2.2.6 #1021
+67
−22
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
node and browser
package.json
updated to set therepository.type
property 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
clientAppId
property is now correctly set in theISessionInfo
objects returned by thehandleIncomingRedirect
function inClientAuthentication
and in theSession
class.node
keepAlive
option (introduced in v2.2.0) is now correctly observed in a script using the Client Credentials flow (i.e. using aclientId
and aclientSecret
to log in). It previously was disregarded, and theSession
always self-refreshed in the backgroundFull Changelog: v2.2.3...v2.2.4
Bugfix
node and browser
clientId
from ID Tokenazp
claim: the parsing of the ID Token payload was not correctly extracting theclientId
from theazp
claim. As a result,session.info.clientAppId
was not being initialised upon successful login, which prevented theidp
logout 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
DPoP
when 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
Session
self-refreshing in NodeJS. To do so, a newparameter is added to the constructor:
Session({ keepAlive: false })
. This preventsthe
Session
setting 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
fetch
function is used instead of@ inrupt/universal-fetch
.This means this library now only works with Node 18 and higher.
Session
class no longer extendsEventEmitter
. Instead, it exposes anevents
attribute implementingEventEmitter
. We do not recommend to useSession
instance'sevents
attribute as an arbitrary events emitter,and encourage users to only use the supported events and documented API.
Session
methodsonLogin
,onLogout
,onError
,onSessionRestore
,onSessionExpiration
andonNewRefreshToken
have been removed. They are replaced by calls to
session.events.on
, using the appropriate event name.Session
constructor changes:onNewRefreshToken
parameter is no longer supported. Its usage is replaced by callingsession.events.on
using the
EVENTS.NEW_REFRESH_TOKEN
constant as a first parameter, and a callback handling the token as asecond parameter.
useEssSession
parameter is no longer supported.getClientAuthenticationWithDependencies
is no longer exported as part of the public API, and is now internal-only.@ inrupt/oidc-client-ext
is 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-typescript2
to@ 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: