Make it simpler for customers to investigate Blazor Auth issues

[mkArtakMSFT]

There have been many issues customers run into, where it's hard to understand what is the underlying issue. Whether it's a configuration issue or framework issue. This issue will be used to track the work for simplifying such investigations.

Thanks for contacting us.

We're moving this issue to the .NET 7 Planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

[Lukazoid]

I feel like even allowing setup of the oidc-client logger would help a lot.

Currently I have a token endpoint returning a valid access_token and id_token but the UI simply says: "There was an error trying to log you in: ''", with nothing in the console or VS output window, really not sure how to investigate this further.

[andrew-tevent]

Agree, AuthenticationService.js should have config options which allow the Oidc.Log.Logger = console and Oidc.Log.LogLevel = ?. This would at least be a start. It's a pain that you have to build a custom version of AuthenticationService to turn the OIDC logging on.

[mkArtakMSFT]

Moving to the RC1 milestone, as @javiercn has some work on hand which is going to improve this. Let's close this issue when the related PRs get merged.

[javiercn]

We did add logging support on the JS libraries which covers this