Getting "An account could not be found for the provided user ID." error while clicking on forgot password link when using identity provider as "User ID signin"

Question

Getting "An account could not be found for the provided user ID." error while clicking on forgot password link when using identity provider as "User ID signin"

Jignesh Patel 56

Hi,

I've created signin workflow and set up Identity provider as "User ID signin". SignIn functionality is working correctly but from SignIn page when clicking on Forgot password link
after that added Username & Email address. After adding code received on email it's verified code correctly but in last step while clicking on "Continue" it's giving an error "An account could not be found for the provided user ID."

Marilee Turscak-MSFT 37,206 Reputation points Microsoft Employee Moderator

2021-10-06T23:21:23.367+00:00

To debug this, please enable app insights and check what value of "unique_name" is coming back to B2C when you federate. Depending on the user, which could be a cloud user or a federated (with ADFS using your corporate AAD) you could have different values of "unique_Name"

https://learn.microsoft.com/en-us/azure/active-directory-b2c/troubleshoot-with-application-insights

After you know what "unique_Name" is coming back you should look at the graph data to see if there is a user with that email address in the signInName. It will fail if it is not there.

1 answer

Your answer

Marilee Turscak-MSFT 37,206 Reputation points Microsoft Employee Moderator

2021-10-06T23:21:23.367+00:00

To debug this, please enable app insights and check what value of "unique_name" is coming back to B2C when you federate. Depending on the user, which could be a cloud user or a federated (with ADFS using your corporate AAD) you could have different values of "unique_Name"

https://learn.microsoft.com/en-us/azure/active-directory-b2c/troubleshoot-with-application-insights

After you know what "unique_Name" is coming back you should look at the graph data to see if there is a user with that email address in the signInName. It will fail if it is not there.

Answer 1

Jignesh Patel 56

Thanks @Marilee Turscak-MSFT for your response.

As of now we kept this requirement on hold and we implemented sign in based on Email address instead of Username. And that thing is working fine same as before. In future if we will implement Signin based on Username then will look in detail.

Again thanks for your contribution.

Share via

Getting "An account could not be found for the provided user ID." error while clicking on forgot password link when using identity provider as "User ID signin"

1 answer

Your answer