Earlier, getBackwardsCompatibleUserInfo would throw an error in case the session and user id did not match. This would cause an issue when using MFA since the session user id would not change during the second factor (and if the frontend SDK being used has 1.17 as the max CDI)
Test Plan
Added a test that simulates the 2fa scenario and makes sure no error is thrown
Added a test that queries the login API (of linked user) with the older FDI and makes sure that the returned user matches the session user ID.
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.
Summary of change
Earlier,
getBackwardsCompatibleUserInfowould throw an error in case the session and user id did not match. This would cause an issue when using MFA since the session user id would not change during the second factor (and if the frontend SDK being used has 1.17 as the max CDI)Test Plan
Checklist for important updates
coreDriverInterfaceSupported.jsonfile has been updated (if needed)lib/ts/version.tsfrontendDriverInterfaceSupported.jsonfile has been updated (if needed)package.jsonpackage-lock.jsonlib/ts/version.tsnpm run build-prettyrecipe/thirdparty/providers/configUtils.tsfile,createProviderfunction.git tag) in the formatvX.Y.Z, and then find the latest branch (git branch --all) whoseX.Yis greater than the latest released tag.add-ts-no-check.jsfile to include thatsomeFunc: function () {..}).