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

🐛 set the correct default factor for recovery flows #303

Conversation

mauriciocastillosilva-okta
Copy link
Contributor

  • Forgot Password and Unlock Account flows were defaulting to email for the recovery factor. If a user press 'Enter' in the for, we were sending a request with email as a factor, even if email was not on the available factors (features.emailRecovery=false).
  • The fix is to default to the factor that is first on the list

Resolves: OKTA-141184

- Forgot Password and Unlock Account flows were defaulting to email for the recovery factor. If a user press 'Enter' in the for, we were sending a request with email as a factor, even if email was not on the available factors (features.emailRecovery=false).
- The fix is to default to the factor that is first on the list

Resolves: OKTA-141184
Copy link
Contributor

@gowthamidommety-okta gowthamidommety-okta left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! :shipit:

Copy link
Contributor

@rchild-okta rchild-okta left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm 🚀

}
if (emailEnabled) {
this.$el.addClass('forgot-password-email-enabled');
formChildren.push(this.createRecoveryFactorButton('email-button', 'password.forgot.sendEmail',
Enums.RECOVERY_FACTOR_TYPE_EMAIL, this));
this.setDefaultFactorType(Enums.RECOVERY_FACTOR_TYPE_EMAIL);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Double checking - is this the right order of preference (SMS, then call, then email)?

Edit: Looking at the test cases, this is indeed the intended behavior. Good!

@mauriciocastillosilva-okta mauriciocastillosilva-okta merged commit 7d83282 into okta:master Sep 21, 2017
@mauriciocastillosilva-okta mauriciocastillosilva-okta deleted the mcs-okta-141184-defaultRecoveryFactorIssue branch October 4, 2017 21:50
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.

None yet

3 participants