Accessing AuthenticationStateProvider from DbContext or Startup.cs

[mrlife]

Is it possible to access Blazor's AuthenticationStateProvider from a DbContext or in Startup.Configure()?

I receive this error:

GetAuthenticationStateAsync was called before SetAuthenticationState.

@Blackleones, did you ever get this line to work in your DbContext? ref #17442 (comment)

var userId = await _currentUserService.GetUserId();

[javiercn]

@mrlife thanks for contacting us.

I'm not sure what you are trying to achieve, but the answer in general is no, since it needs to be accessed within the scope/lifetime of a Blazor application.

[mrlife]

@javiercn Thanks for getting back to me. What ultimately may help is to understand why accessing a scoped service in Startup.Configure() appears to be a different instance of the service that is created when the Blazor app is loaded. I have a Guid that's set in the service's constructor, and it's different when accessed within the Blazor workflow and within Startup.Configure(). Aren't scoped services created once per HTTP request?

[javiercn]

@mrlife Blazor creates its own scope every time a new session is established (when you start a circuit) and is not associated with an HTTP request. You can only operate within the context of the Blazor scope either inside a component or a circuit handler.

In addition to that, If your component inherits from OwningComponentBase<T> the T in the Service property has it's own independent scope.

[mrlife]

@javiercn Thank you for letting me know about these specifics of service scope in a Blazor application. I didn't get out of the docs what you explained... perhaps it's a good candidate to be added there?

We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.

[mkArtakMSFT]

Thanks for your feedback, @mrlife.
Moving this to Backlog so that we can evaluate later whether the current documentation is misleading for others too or not. If yes, we will try to improve it then.