Cannot complete registration or any other process requiring email and validations.

[Unsigned-Char]

Describe the bug

1. The documentation is not clear about using SendGrid of another email provider. Providing working elements for each case would have a significant impact since each case seems to be partially implemented.

2. After implementing an email client, the registration and other processes like email updates and password changes, etc., that rely on security tokens to be generated, wouldn't and cannot work under the current architecture.

• Mainly, the UserManager and TokenProvider are different instances between the generation and validation of those tokens since they are disposed of and instantiated on each use of services.
  

• The tokens must be validated by the same instance that generated them and the user must also have an unchanged SecurityStamp otherwise the TokenProvider validation process always returns InvalidToken.
  

To Reproduce
Steps to reproduce the behavior:

1. Run TheIdServer
2. Register a new user, rinse and repeat.

Expected behavior
A functional registration and validation process where the user receives an email to confirm its address or changes.
The link he receives and the token it contains must be valid upon confirmation.

Logs
If applicable, add logs to help explain your problem.

Platform (please complete the following information):

• OS: Windows 10 Pro
• .Net Core Version 5.0.9

Additional context

[aguacongas]

Hi @Unsigned-Char , thx to contribute again.
Can you post your configuration and tell me how you implement the service please ?

[Unsigned-Char]

The following :

• Windows 10 Pro
• Clean Visual Studio 2019 Community
• dot.NET SDK 5.0.9
• A clone of Master
• No change to appSettings.json except adding my SendGrid credentials.

I simply compiled the solution and ran TheIdServer in debug mode.

I used the admin interface to register and change the email address afterward. In either case, the token validation always returns an invalid token response.

ConfirmEmailChange.cshtml.cs : 48:13 : var result = await _userManager.ChangeEmailAsync(user, email, code);

ConfirmEmail.cshtml.cs : 43:13 : var result = await _userManager.ConfirmEmailAsync(user, code);

I don't have the debug information for Microsoft's UserManager, but I'm guessing the tokens cannot be validated because they cannot be found, the validators or stores are different instances than those when they were created.

[aguacongas]

Ok, the issue is in the Identity store implementation, I'll do my best to fix it