Issue related to the silentRequestTimeout in AuthenticationService.js (Microsoft.AspNetCore.Components.WebAssembly.Authentication)

[ks1234-bit]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

Hi there! I have a problem with the Microsoft.AspNetCore.Components.WebAssembly.Authentication(v8.0.8) package. More specifically with the AuthenticationService.js. The problem is the following - whenever I open my Blazor app inside of an iframe I have to wait 10 seconds before the authentication starts.
Here is the place where the timeout gets set

return t.prototype.navigate = function(t) { if (t && t.url) { var e = t.silentRequestTimeout || 1e4; i.Log.debug("IFrameWindow.navigate: Using timeout of:", e), this._timer = window.setTimeout(this._timeout.bind(this), e), this._frame.src = t.url } else this._error("No url provided"); return this.promise }

the t.silentRequestTimeout is always undefined so it takes 1e4. Is there a way to override the value of t.silentRequestTimeout to set it to 0?

Expected Behavior

Is there a way to override the value of t.silentRequestTimeout to set it to 0? That property doesn't seem to be exposed by the AuthenticationService.js, but probably I'm missing something and there is a way to configure it somehow. If no, then do you have any suggestions on how to remove that timeout?

Steps To Reproduce

No response

Exceptions (if any)

No response

.NET Version

9.0.204

Anything else?

No response

[MackinnonBuck]

Thanks for reaching out, @ks1234-bit.

Could you please take a look at https://learn.microsoft.com/aspnet/core/blazor/security/webassembly/standalone-with-microsoft-accounts?view=aspnetcore-9.0#login-mode and see if this resolves your issue?

[dotnet-policy-service]

Hi @@ks1234-bit. 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.