Bump supertokens-node from 13.6.0 to 14.1.1 in /server

[dependabot]

Bumps supertokens-node from 13.6.0 to 14.1.1.

Release notes

Sourced from supertokens-node's releases.

v14.1.0

What's Changed

• feat: Add a helper function to read the original request from the user context inside overrides by @​nkshah2 in supertokens/supertokens-node#569

Full Changelog: supertokens/supertokens-node@v14.0.2...v14.1.0

v14.0.2

What's Changed

• feat!: make loading access token from the request overrideable by @​porcellus in supertokens/supertokens-node#562

Full Changelog: supertokens/supertokens-node@v14.0.1...v14.0.2

v14.0.0

What's Changed

• feat: optional password validation in updateEmailOrPassword by @​iresharma in supertokens/supertokens-node#554
• feat: access token to jwt base by @​porcellus in supertokens/supertokens-node#531
• test: fix test failures in CI by @​porcellus in supertokens/supertokens-node#558

Full Changelog: supertokens/supertokens-node@v13.6.0...v14.0.0

Changelog

Sourced from supertokens-node's changelog.

[14.1.1] - 2023-05-24

Added

• Adds additional debug logs whenever the SDK throws a TRY_REFRESH_TOKEN or UNAUTHORISED error to make debugging easier

[14.1.0] - 2023-05-23

Changes

• Added a new getRequestFromUserContext function that can be used to read the original network request from the user context in overridden APIs and recipe functions

[14.0.2] - 2023-05-11

Changes

• Made the access token string optional in the overrideable getSession function
• Moved checking if the access token is defined into the overrideable getSession function

[14.0.1] - 2023-05-11

• Fixes an issue where API key based login with dashboard would return invalid API key even if the entered API key was valid

[14.0.0] - 2023-05-04

Breaking Changes

• Added support for CDI version 2.21
• Dropped support for CDI version 2.8-2.20
• Changed the interface and configuration of the Session recipe, see below for details. If you do not use the Session recipe directly and do not provide custom configuration, then no migration is necessary.
• getAccessTokenPayload will now return standard (sub, iat, exp) claims and some SuperTokens specific claims along the user defined ones in getAccessTokenPayload.
• Some claim names are now prohibited in the root level of the access token payload
  • They are: sub, iat, exp, sessionHandle, parentRefreshTokenHash1, refreshTokenHash1, antiCsrfToken
  • If you used these in the root level of the access token payload, then you'll need to migrate your sessions or they will be logged out during the next refresh
  • These props should be renamed (e.g., by adding a prefix) or moved inside an object in the access token payload
  • You can migrate these sessions by updating their payload to match your new structure, by calling mergeIntoAccessTokenPayload
• New access tokens are valid JWTs now
  • They can be used directly (i.e.: by calling getAccessToken on the session) if you need a JWT
  • The jwt prop in the access token payload is removed
• Changed the Session recipe interface - createNewSession, getSession and refreshSession overrides now do not take response and request and return status instead of throwing
• Renamed accessTokenPayload to customClaimsInAccessTokenPayload in SessionInformation (the return value of getSessionInformation). This reflects the fact that it doesn't contain some default claims (sub, iat, etc.)

Configuration changes

• Added useDynamicAccessTokenSigningKey (defaults to true) option to the Session recipe config
• Added exposeAccessTokenToFrontendInCookieBasedAuth (defaults to false) option to the Session recipe config
• JWT and OpenId related configuration has been removed from the Session recipe config. If necessary, they can be added by initializing the OpenId recipe before the Session recipe.

Interface changes

... (truncated)

Commits

• b3e1c19 adding dev-v14.1.1 tag to this commit to ensure building
• 58e70e7 chore: add extra debug logs (#571)
• 44024de adding dev-v14.1.0 tag to this commit to ensure building
• 8a4418f feat: Add a helper function to read the original request from the user contex...
• ae9be01 adding dev-v14.0.2 tag to this commit to ensure building
• 1825eb9 feat!: make loading access token from the request overrideable (#562)
• d0df54f fixes changelog
• 7238d1d adding dev-v14.0.1 tag to this commit to ensure building
• 451c7cb fix: Dashboard API key based login always failing with invalid API key (#561)
• 77607b7 adding dev-v14.0.0 tag to this commit to ensure building
• Additional commits viewable in compare view

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 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 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)

[dependabot]

Superseded by #95.