Blazor Authenticate Exception_wasthrown

[hannespreishuber]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

I migrate a blazor 8 to 9 with SSR and Authentication. As I stuck with issues (eg infinit reload of login) I created a new Blazor Project
Template Blazor Web App, drop down Server per Page

create Database
try to create User
fail with exception in Identityredirectmanager.cs

Expected Behavior

working default Visual Studio Template

Steps To Reproduce

see above

Exceptions (if any)

.NET Version

9.0.100

Anything else?

No response

[mkArtakMSFT]

Thanks for contacting us. The exception that you're observing is going to be handled by the framework. It's just a debugger behavior change that is causing the break, which you can safely continue. We're going to improve this experience in the upcoming .NET 9 servicing release. You can learn more about this from the PR description: #58573

[mkArtakMSFT]

As for the redirection cycle that you've observed, that usually is experience when there is a mismatch between the authentication states between the server and the client, which leads to the client to try to redirect to the server for authentication, which in turn, thinking that the user is authenticated, redirects the user back to the page where all this started from. So the cycle repeats.

If you aren't able to figure out the cause for the mismatch, feel free to share a minimal repro project and we can take a look.

[hannespreishuber]

it is just click click click project

https://github.com/[hannespreishuber/BlazorApp2GlobalAuthDeleteMe](https://github.com/hannespreishuber/BlazorApp2GlobalAuthDeleteMe)

create Database- run
Create a user account - Exception

[javiercn]

@hannespreishuber the exception is expected.

The framework catches it. The debugger is simply stopping on it, if you run without debugging, the debugger shouldn't break on the exception, and you should be able to execute without pause.

Do you still see an issue when you run without debugging? (Exception and/or login cycle).

[dotnet-policy-service]

Hi @hannespreishuber. We have added the "Needs: Author Feedback" label to this issue, which indicates that we have an open question for you before we can take further action. This issue will be closed automatically in 7 days if we do not hear back from you by then - please feel free to re-open it if you come back to this issue after that time.

[dotnet-policy-service]

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment. If it is closed, feel free to comment when you are able to provide the additional information and we will re-investigate.

See our Issue Management Policies for more information.