search

inrupt / solid-client-notifications-js

solid-client-notifications-js-git-main-inrupt.vercel.app
MIT License
2 stars 3 forks source link

chore(deps): bump @inrupt/solid-client-authn-browser from 2.2.1 to 2.2.4 in /e2e/browser/test-app #1003

Closed dependabot[bot] closed 3 months ago

dependabot[bot] commented 3 months ago

Bumps @inrupt/solid-client-authn-browser from 2.2.1 to 2.2.4.

Release notes

Sourced from @​inrupt/solid-client-authn-browser's releases.

v2.2.4

Bugfixes

node and browser

  • The clientAppId property is now correctly set in the ISessionInfo objects returned by the handleIncomingRedirect function in ClientAuthentication and in the Session class.

node

  • The keepAlive option (introduced in v2.2.0) is now correctly observed in a script using the Client Credentials flow (i.e. using a clientId and a clientSecret to log in). It previously was disregarded, and the Session always self-refreshed in the background

Full Changelog: https://github.com/inrupt/solid-client-authn-js/compare/v2.2.3...v2.2.4

v2.2.3

Bugfix

node and browser

  • Fix parsing clientId from ID Token azp claim: the parsing of the ID Token payload was not correctly extracting the clientId from the azp claim. As a result, session.info.clientAppId was not being initialised upon successful login, which prevented the idp logout of the session from working as expected.

Full Changelog: https://github.com/inrupt/solid-client-authn-js/compare/v2.2.2...v2.2.3

v2.2.2

Bugfix

node

  • Maintain token type in 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) is now 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 logging the session back in on load from storage, causing authentication issues.

Full Changelog: https://github.com/inrupt/solid-client-authn-js/compare/v2.2.1...v2.2.2

Changelog

Sourced from @​inrupt/solid-client-authn-browser's changelog.

2.2.4 - 2024-06-24

Bugfix

node and browser

  • Fix the initialization of clientAppId in ISessionInfo objects: clientAppId property of the ISessionInfo interface, although present, was not being set either in the ISessionInfo objects returned by the handleIncomingRedirect function in ClientAuthentication, or in the Session class.

Bugfix

node

  • The keepAlive option (introduced in v2.2.0) is now correctly observed in a script using the Client Credentials flow (i.e. using a clientId and a clientSecret to log in). It previously was disregarded, and the Session always self-refreshed in the background.

    Note that there still is a timeout being set to notify of session expiration, causing NodeJS to wait for the end of the session before closing a terminal. This can be avoided by logging the session out explicitly:

      const session = new Session();
  await session.login({
    oidcIssuer: ...,
    clientId: ...,
    clientSecret: ...,
  });

    will hang until the session expires, while

      const session = new Session();
  await session.login({
    oidcIssuer: ...,
    clientId: ...,
    clientSecret: ...,
  });
  await session.logout();

    will close when logout is complete.

2.2.3 - 2024-06-20

Bugfix

node and browser

... (truncated)

Commits


Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot will merge this PR once it's up-to-date and CI passes on it, as requested by @acoburn.

Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)