I use Azure AD B2C for identity management in my apps and one of those apps is a Blazor WASM (Standalone) app. Things work fine for the most part but in the Blazor WASM, on user authentication, the user is first redirected to the home page of my app at https://myapp.com and then to https://myapp.com/authentication/login-callback.
This still works fine because once my app gets the tokens, it still redirects to the home page at https://myapp.com but in the meantime, the UI gives user confusing feedback.
As with most Blazor WASM apps, my app shows a loading animation initially which then goes away during user authentication but once the authentication is done and user gets redirected to the home page at https://myapp.com, the loading animation shows up again. And then it disappears again when the URL changes to https://myapp.com/authentication/login-callback.
When I check the redirect URI's on Azure AD B2C > App Registrations > Authentication, the following is what I see:
What would cause the user to be redirected to the home page of my app rather than /authentication/login-callback? I'm sure this is due to an issue with a setting somewhere but so far I couldn't find it and I'd appreciate some suggestions. Thanks.