Rishabh Poddar

# How would factorsSetUpByTheUser be determined when calling getMFARequirementsForAuth? - Each recipe will tell the MFA recipe if the factor controlled by that recipe is setup. - For example, if...

# Implementation of isAllowedToSetupFactor - Returns true if have completed everything in the `mfaRequirementsForAuth` || (if the next step in `mfaRequirementsForAuth` cannot be completed && the next step includes input...

# How would the frontend pre built UI sdk show the factor picker screen with custom factor IDs (or for redirection): - In MFA.init, we have a overridable function like...

# Edit: 19th oct, 2023 We decided to drop the custom vs in built factor typing in the node sdk, and just make the FirstFactor type a string

# EDIT: 23rd November, 2023 For the default implementation of `isAllowedToSetupFactor`: - if the next array is empty, then we should allow - if not and any of the items...

hey @govindraj111 could you please describe the solution before I assign it to you?

hey @yogurtearl whilst null safety is a big positive, using kotlin for the core is not a priority for us at the moment. That being said, im keeping this issue...

Hey @debjitk only the core midroservice is in Java. The core microservice forms just one part of SuperTokens. A lot of the logic for how SuperTokens works in the backend...

Java SDK is probably next year sometime. We do support SSO in the sense that you can integrate with any OIDC provider. > Also, the documentation needs to be more...

Until this is implemented on our end, the way you can achieve this is to store info about the user in your own db by overriding the sign up API....