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

return MFA_REQUIRED signIn with deviceToken #364

Open
ghost opened this issue May 10, 2023 · 0 comments
Open

return MFA_REQUIRED signIn with deviceToken #364

ghost opened this issue May 10, 2023 · 0 comments
Labels
bug Something isn't working

Comments

@ghost
Copy link

ghost commented May 10, 2023

Describe the bug?

const authClient = getAuthClient();
const options = {
    multiOptionalFactorEnroll: false,
    warnBeforePasswordExpired: false,
};

const context = { deviceToken };
return await authClient.signIn({ username, password, options, context });

the above code executes fine until when our okta admin go-ahead and add a new behavior ("NEW_DEVICE") in OKTA console. After the new behavior got added to OKTA, whenever a user tries to login OKTA transaction response has MFA_REQUIRED and I think deviceToken is ignored in the request.

image

What is expected to happen?

OKTA should consider / respect deviceToken sent as part of the request headers as long it same when sent along with authentication request.

What is the actual behavior?

SDK shouldn't expect MFA_REQUIRED for every authentication request when NEW_DEVICE behavior is added in OKTA dashboard / console.

Reproduction Steps?

  1. Create OIDC Application
  2. Create SMS / Email MFA Factors
  3. Add a Behavior trigger MFA for NEW_DEVICE
  4. use custom signIn using getAuthClient and pass username, password, deviceToken in context

Additional Information?

No response

SDK Version

v2.6.0

Build Information

No response

@ghost ghost added the bug Something isn't working label May 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

0 participants