You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please create documentation that shows the steps to use Blazor Hosted prerendering when using Azure Ad authentication. Currently the error page says that it can't get CascadingAuthenticationState cascading parameter. If I copy the builder.Services.AddMsalAuthentication(options =>
{
builder.Configuration.Bind("AzureAd", options.ProviderOptions.Authentication);
options.ProviderOptions.DefaultAccessTokenScopes.Add("scope_uri");
});
the error page says that it can't perform JS interop during server-side prerendering.
My index page does not even require authorization.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
ID: 329a19ef-fb46-1f6b-a734-fa1c1334b1e5
Version Independent ID: 3fa4318a-3c11-c1d8-bf24-ddc6d8441ca2
I'll add a cross-link to that to the WASM Security Overview topic as well. What I might do in the end is make an INCLUDE file out of that section and place a copy of the entire section in both the Security Additional Scenarios doc and this Prerendering and Integration doc. I'll make a note to myself to check on doing that when I reach that topic for more work later. Thanks for commenting on this.
Please create documentation that shows the steps to use Blazor Hosted prerendering when using Azure Ad authentication. Currently the error page says that it can't get CascadingAuthenticationState cascading parameter. If I copy the builder.Services.AddMsalAuthentication(options =>
{
builder.Configuration.Bind("AzureAd", options.ProviderOptions.Authentication);
options.ProviderOptions.DefaultAccessTokenScopes.Add("scope_uri");
});
the error page says that it can't perform JS interop during server-side prerendering.
My index page does not even require authorization.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
The text was updated successfully, but these errors were encountered: