You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If maxPasswordHistory is set to a value != 0, the token request does not work as expected. It appears to be incorrectly interpreted as a password change request, as a result no token is created.
Steps to reproduce
To reproduce the issue you have to set maxPasswordHistory in index.js to a value != 0:
maxPasswordHistory: 5
Then you need to request a token for a user with MFA enabled:
🚀 You can help us to fix this issue faster by opening a pull request with a failing test. See our Contribution Guide for how to make a pull request, or read our New Contributor's Guide if this is your first time contributing.
New Issue Checklist
Issue Description
If maxPasswordHistory is set to a value != 0, the token request does not work as expected. It appears to be incorrectly interpreted as a password change request, as a result no token is created.
Steps to reproduce
To reproduce the issue you have to set
maxPasswordHistory
inindex.js
to a value != 0:maxPasswordHistory: 5
Then you need to request a token for a user with MFA enabled:
This is the response:
If you remove
maxPasswordHistory
the token is sent as expected.Actual Outcome
sendSMS
callback is not called and this is the current result ifmaxPasswordHistory
is != 0:Expected Outcome
sendSMS
callback returns the token and this is the expected response to the token request:Environment
Node:
18.20.5
Server
7.4.0
Ubuntu 20.04
Digital Ocean
Database
MongoDB
6
Digital Ocean
The text was updated successfully, but these errors were encountered: