20 Second Delay Before Sign-In Page

[Griminal]

I am building a Blazor WebAssembly (WASM) app and am using the Okta-hosted sign-in page (per the example on the Okta Github titled ‘Blazor WebAssembly & Okta-Hosted Sign-In Page Example’).

When I go to my app, the App.razor has a 10 second delay before it redirects to my /authentication/login page. Once it hits the /authentication/login page, there is another 10 second delay before it redirects to the Okta sign-in page.

I noticed that when the App.razor page loads and the /authentication/login page shows, an HTTP error is thrown, when I go to the Okta page showing the error, the page shows ‘Error: The client specified not to prompt, but the user is not logged in.’

I am assuming that because there isn’t an active token, it times out twice and then fails over to the Okta auth page. I can see prompt=none in the OAuth authorize request, but I have been unable to change that.

How can I eliminate the two 10 second delays before I get to the Okta sign-in page?

Thanks

EDIT: I should note that when there is a valid token, my app loads super quick (under one second typically), going from App.razor to my main page.

[akash-okta]

Hey there,

My name is Akash from Okta.

To ensure that we are referring to the same sample, could you please confirm if this is the sample application that you are using? - samples-blazor/web-assembly/okta-hosted-login at master · okta/samples-blazor · GitHub

Otherwise, please try this application and check whether you are able to reproduce the same error.