Port ForbidAsync changes to 2.0.x

Question

Port ForbidAsync changes to 2.0.x

jkotalik opened this issue 8 years ago · 6 comments

Answer 1 · 2017-09-15T20:08:33.000Z

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.

Answer 2 · 2017-09-15T20:09:01.000Z

@jkotalik / @HaoK / @Tratcher - Do we need to consider any quirks mode switch here? Is it even remotely possible that anyone would be relying on the 2.0.0-rtm behavior?

Answer 3 · 2017-09-15T20:11:26.000Z

No, Forbid already falls back to Challenge if not set.

Answer 4 · 2017-09-21T17:21:14.000Z

Looks like this was fixed in #939, right @jkotalik ?

Answer 5 · 2017-09-21T17:27:22.000Z

Yes we did!

Answer 6 · 2017-10-23T22:49:01.000Z

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:

aspnet/Announcements#274 (info)
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