This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(96, 71%, 19%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETC%3C/text%3E%3C/svg%3E)
I have successfully implemented the Auth process for Blazor WASM using this article - https://github.com/JeepNL/Blazor-WASM-Identity-gRPC
The strange behavior I'd like to correct is that the Index pages appears for a second or 2 and THEN i'm redirected to the Login page, where I am Authenticated and returned to the Index.
Is there a way to have the Auth process kick in sooner?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(76.8, 76%, 17%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EYY%3C/text%3E%3C/svg%3E)
Hi,@Tim Cadieux ,
you can try to click F12 and check the Network to find which request takes more time.
Hi, I'm not sure I understand the point...I would have thought that Authentication would always be the first thing to fire and using the [Authorize] decorator on my Index page would prevent if from ever being displayed until the user is Authenticated.
Hi,@Tim Cadieux ,
Network will show the time for each request,by checking the time,you can find which request or requests need more time.Then you can check the code of the request and try to reduce the time for the request.
The problem is that Authentication takes first load then other contents
It you enabled the authentication in your project.
It because you add authenticationVIew in App.razor.
I don't think there is any solution on this right now.