Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: fix the session revocation throwing when email verification links in a non-default tenant #939

Merged
merged 2 commits into from
Oct 7, 2024

Conversation

porcellus
Copy link
Collaborator

@porcellus porcellus commented Oct 7, 2024

Summary of change

  • Fixes an issue where revoking sessions for a specific tenant didn't work well
  • Fixes an issue where the automatic session revocation after linking didn't work across all tenants

Related issues

  • Issue reported by a user over email

Test Plan

Tests added in backend-sdk-testing PR

Documentation changes

N/A

Checklist for important updates

  • Changelog has been updated
  • coreDriverInterfaceSupported.json file has been updated (if needed)
    • Along with the associated array in lib/ts/version.ts
  • frontendDriverInterfaceSupported.json file has been updated (if needed)
  • Changes to the version if needed
    • In package.json
    • In package-lock.json
    • In lib/ts/version.ts
  • Had run npm run build-pretty
  • Had installed and ran the pre-commit hook
  • If new thirdparty provider is added,
    • update switch statement in recipe/thirdparty/providers/configUtils.ts file, createProvider function.
    • add an icon on the user management dashboard.
  • Issue this PR against the latest non released version branch.
    • To know which one it is, run find the latest released tag (git tag) in the format vX.Y.Z, and then find the latest branch (git branch --all) whose X.Y is greater than the latest released tag.
    • If no such branch exists, then create one from the latest released branch.
  • If have added a new web framework, update the add-ts-no-check.js file to include that
  • If added a new recipe / api interface, then make sure that the implementation of it uses NON arrow functions only (like someFunc: function () {..}).
  • If added a new recipe, then make sure to expose it inside the recipe folder present in the root of this repo. We also need to expose its types.
  • If added a new entry point, then make sure that it is importable by adding it to the exports in package.json

Copy link

Deploying supertokens-node-pr-check-for-edge-function-compat with  Cloudflare Pages  Cloudflare Pages

Latest commit: e12a830
Status: ✅  Deploy successful!
Preview URL: https://28000663.supertokens-node-b95.pages.dev

View logs

@rishabhpoddar rishabhpoddar merged commit 03988c7 into 20.1 Oct 7, 2024
6 of 7 checks passed
@rishabhpoddar rishabhpoddar deleted the fix/ev_linking_session_revocation branch October 7, 2024 11:57
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.

2 participants