microsoft inbuilt azuread authentication in asp.net mvc getting error

raj raj

I am using microsoft inbuilt authorization in asp.net mvc.

I am using below call in startup.auth.cs. I am getting prompt in mobile for authorization after allowing it is not redirecting in default page.

private static string clientId = ConfigurationManager.AppSettings["ida:ClientId"];
private static string aadInstance = EnsureTrailingSlash(ConfigurationManager.AppSettings["ida:AADInstance"]);
private static string tenantId = ConfigurationManager.AppSettings["ida:TenantId"];
private static string postLogoutRedirectUri = ConfigurationManager.AppSettings["ida:PostLogoutRedirectUri"];
private static string authority = aadInstance + tenantId;

public void ConfigureAuth(IAppBuilder app)
{
app.SetDefaultSignInAsAuthenticationType(CookieAuthenticationDefaults.AuthenticationType);

app.UseCookieAuthentication(new CookieAuthenticationOptions());

app.UseOpenIdConnectAuthentication(
new OpenIdConnectAuthenticationOptions
{
ClientId = clientId,
Authority = authority,
PostLogoutRedirectUri = postLogoutRedirectUri
});
}

2 Replies

Know the answer? Post it — somebody with the same question will find it here.

raj raj3y ago
I am getting below error
Deepak Rawat3y ago
The code you provided sets up authentication and authorization using OpenID Connect with Azure Active Directory (AAD) in an ASP.NET MVC application. To troubleshoot the issue where the default page is not being redirected to after authorization on mobile, you can consider the following: Verify the post-authorization redirect URI: Ensure that the postLogoutRedirectUri value in your appsettings.json or configuration file is correct and matches the URI of your default page. Double-check that the URI is accessible and does not contain any typos or missing components. Check mobile browser settings: On the mobile device, check if the browser settings allow pop-ups or redirects. Some mobile browsers have settings that prevent automatic redirects or pop-ups, which could affect the behavior of the authorization flow. Check browser compatibility: Ensure that the mobile browser being used is compatible with the authentication and authorization flow you have implemented. Some older mobile browsers may not fully support the necessary features for seamless authentication and redirect behavior. Debugging and logging: Enable logging and debugging in your application to capture any errors or exceptions that may be occurring during the authentication and redirect process. Review the logs to identify any issues or error messages that could explain the unexpected behavior. Test on different mobile devices and browsers: Try testing the application on different mobile devices and browsers to see if the issue is specific to a particular combination. This can help identify if the problem is related to the mobile device or browser settings. By following these steps and investigating the specific details of the issue, you should be able to identify the cause and resolve the problem with the authorization flow not redirecting to the default page after approval on mobile.