Port ChangePhoneNumber fix to 2.0.1

[HaoK]

Port #1388

Change: b7d5a46

[kinosang]

I wanna to know when will this patch releases?

or should I use the nightly build before you publish it?

[Eilon]

This patch bug is approved for the 2.0.x patch. Please send a PR to the feature/2.0.1 branch and get it reviewed and merged. When we have the rel/2.0.1 branches ready please port the commit to that branch.

[Eilon]

@kinosang we're working on setting up a feed for the upcoming 2.0.x patch that will have this fix.

[HaoK]

Pushed b7d5a46 to feature/2.0.1

[Eilon]

Hi, we have a public test feed that you can use to try out the ASP.NET/EF Core 2.0.3 patch!

To try out the pre-release patch, please refer to the following guide:

• ASP.NET/EF Core 2.0.3 patch pre-release test feed Announcements#274 (info)
• ASP.NET/EF Core 2.0.3 patch pre-release test feed - discussion dotnet/aspnetcore#2254 (discussions and questions)

We are looking for feedback on this patch. We'd like to know if you have any issues with this patch by updating your apps and libraries to the latest packages and seeing if it fixes the issues you've had, or if it introduces any new issues. If you have any issues or questions, please reply on this issue to let us know as soon as possible.

Thanks,
Eilon

[kevinchalet]

Erf, this "patch" introduces a terribad regression: it's no longer possible to create a custom provider for the "phone number tokens" as GenerateChangePhoneNumberTokenAsync() now directly calls the internal Rfc6238AuthenticationService class instead of the usual providers thingy.

Why was it fixed this way?

[blowdart]

@HaoK was this deliberate?