Blazor WASM redirect to page not found after login from OIDC

Question

Blazor WASM redirect to page not found after login from OIDC

Moeen Uddin 0

I have a Blazor WASM app, and i am using IDS(Identity Server) for authorization. After the successful login from IDS i get redirected back to app with the error message "Sorry, there's nothing at this address." User's image

I have setup @attribute [Authorize] on a Counter page for testing but same happens if i use it on Home page. Basiclly this is the message from Router.NotFound component There has been a fix for this here WASM Redirect not working I have tried this but still redirect goes to NotFound This is my redirect uri setting "RedirectUri": "https://localhost:7095/signin-oidc" Redirect uri and grant types is setup on both client and server.

AgaveJoe 29,946 Reputation points

2024-02-21T11:12:04.5666667+00:00

Blazor runs in the browser. Either change the flow and use the client_credentials grant type or to add a Razor Page (Or Controller/View) to handle the redirect from the server. Once authentication then load the Blazor application. See the Identity Server documentation.
Moeen Uddin 0 Reputation points

2024-02-21T12:06:50.2266667+00:00

@AgaveJoe I am using authorization_code as grant type
I following this article from MS docs
https://learn.microsoft.com/en-us/aspnet/core/blazor/security/webassembly/standalone-with-authentication-library?view=aspnetcore-8.0&tabs=visual-studio
Correct me if i am wrong that we dont need to create a page for /signin-oidc.
If i create a new page do you suggest the path to be "/signin-oidc" ?
Sorry I am new to this an example would be helpful.

2 answers

Your answer

AgaveJoe 29,946 Reputation points

2024-02-21T11:12:04.5666667+00:00

Blazor runs in the browser. Either change the flow and use the client_credentials grant type or to add a Razor Page (Or Controller/View) to handle the redirect from the server. Once authentication then load the Blazor application. See the Identity Server documentation.
Moeen Uddin 0 Reputation points

2024-02-21T12:06:50.2266667+00:00

@AgaveJoe I am using authorization_code as grant type
I following this article from MS docs
https://learn.microsoft.com/en-us/aspnet/core/blazor/security/webassembly/standalone-with-authentication-library?view=aspnetcore-8.0&tabs=visual-studio
Correct me if i am wrong that we dont need to create a page for /signin-oidc.
If i create a new page do you suggest the path to be "/signin-oidc" ?
Sorry I am new to this an example would be helpful.

Answer 1

Moeen Uddin 0

I got my answer, i was using wrong redirect url. Correct one: "RedirectUri": "https://localhost:7095/authentication/login-callback" I was using "RedirectUri": "https://localhost:7095/signin-oidc"

Answer 2

Double-check your authentication configuration in your Blazor WASM app, particularly the OIDC options. Make sure that the authority, client ID, and other parameters are correctly configured to match your OIDC provider settings.

Handle Navigation: Ensure that your Blazor app properly handles navigation after authentication. After successful authentication, the OIDC middleware will redirect the user back to your application for Mazer Zone escape room camden. Make sure your application redirects the user to the correct page or route after authentication.

Share via

Blazor WASM redirect to page not found after login from OIDC

2 answers

Your answer