When you reset your IdentityNow password, the system requires you to verify your identity before making any changes. This method of verification, sometimes known as strong authentication, ensures that no one except you can reset your password.
When you're working with strong authentication, you might see the error message: "We're not able to verify your identity."
This might happen for a number of reasons. IdentityNow doesn't give you a precise reason to protect you from hackers who might use a specific message as a clue to impersonating you. For example, if we indicated that you answered a security question incorrectly, a person might keep trying that question until they got the answer right.
Here are some of the reasons why IdentityNow might not be able to verify your identity:
- Your account has been disabled. For help, please contact your administrator.
- You gave an incorrect answer to a security question.
- You provided an incorrect or invalid code.
- You chose a 3rd party option such as Duo but you don't have that integration enabled for your account.
- You typed your user name incorrectly in the previous screen.
Locking Password Resets
To further protect your account, IdentityNow sets a limit on the number of times a person can attempt to use strong authentication for password resets. By default, if you or an unauthorized party were unable to verify your identity a certain number of times in a row while attempting to reset your password, IdentityNow does not allow password resets on your account for an interval defined by your administrator; contact your help desk for more information and assistance.
After that period of time, the system allows you to try again.
- Your administrator can configure both the number of allowed attempts and the period of time that password resets are locked.
- In some cases, your administrator might not allow you to change your password from off-network or from untrusted locations. If this is true, you will see an error when you click this option. If you have access, you can connect to your company's VPN to get on the network and resolve this error.
For more information, see: