Delivery API - AuthorizationCodeFlow returns 401 on challange

[bobbyadamski]

Which Umbraco version are you using?

17.0.0

Bug summary

After upgrading to Umbraco 17.0.0 the AuthorizationCodeFlow return 401

Works fine with Umbraco 16.4.3

Specifics

No response

Steps to reproduce

Enable MemberAuthorization:AuthorizationCodeFlow and try to login will fail on Challange and return 401

Expected result / actual result

No response

---

This item has been added to our backlog AB#62652

[github-actions]

Hi there @bobbyadamski!

Firstly, a big thank you for raising this issue. Every piece of feedback we receive helps us to make Umbraco better.

We really appreciate your patience while we wait for our team to have a look at this but we wanted to let you know that we see this and share with you the plan for what comes next.

• We'll assess whether this issue relates to something that has already been fixed in a later version of the release that it has been raised for.
• If it's a bug, is it related to a release that we are actively supporting or is it related to a release that's in the end-of-life or security-only phase?
• We'll replicate the issue to ensure that the problem is as described.
• We'll decide whether the behavior is an issue or if the behavior is intended.

We wish we could work with everyone directly and assess your issue immediately but we're in the fortunate position of having lots of contributions to work with and only a few humans who are able to do it. We are making progress though and in the meantime, we will keep you in the loop and let you know when we have any questions.

Thanks, from your friendly Umbraco GitHub bot 🤖 🙂

[AndyButland]

Related to this breaking change in .NET 10?
https://learn.microsoft.com/en-us/dotnet/core/compatibility/aspnet-core/10/cookie-authentication-api-endpoints

[kjac]

I can reproduce this ... will have a look at fix 👍

[kjac]

Fixed in #21023 for V17.0.1