Issue with Redirecting to Authentication Page in ASP.NET MVC App

ghz 8months ago ⋅ 68 views

Issue with Redirecting to Authentication Page in ASP.NET MVC Application

I'm encountering an issue with redirecting to authentication page in my ASP.NET MVC application. Here's a brief overview of my setup:

  • I have configured my application to use AAD for authentication.
  • I've set up the redirect URIs in the Azure portal to match the ones used in my application (https://localhost:44341/signin-oidc, https://localhost:44387/signin-oidc, https://localhost:44320/signin-oidc).
  • I'm using Microsoft.Owin.Security and Microsoft.Owin.Security.OpenIdConnect for authentication middleware.

However, when I run the application and try to access the authentication-protected routes, I'm not being redirected to the AAD authentication page as expected. Instead, I remain on the same page without any redirection or error message.

Here are the relevant snippets of my code:

Startup.Auth.cs:

public partial class Startup
{
    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 + "/v2.0";

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

        app.UseCookieAuthentication(new CookieAuthenticationOptions());

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

                Notifications = new OpenIdConnectAuthenticationNotifications()
                {
                    SecurityTokenValidated = (context) =>
                    {
                        string name = context.AuthenticationTicket.Identity.FindFirst("preferred_username").Value;
                        context.AuthenticationTicket.Identity.AddClaim(new Claim(ClaimTypes.Name, name, string.Empty));
                        return System.Threading.Tasks.Task.FromResult(0);
                    }
                }
            });
    }

    private static string EnsureTrailingSlash(string value)
    {
        if (value == null)
        {
            value = string.Empty;
        }

        if (!value.EndsWith("/", StringComparison.Ordinal))
        {
            return value + "/";
        }

        return value;
    }
}

Startup.cs:

namespace OidcTestDemo
{
    public partial class Startup
    {
        public void Configuration(IAppBuilder app)
        {
            ConfigureAuth(app);
        }
    }
}

Web.config:

<appSettings>
    <add key="webpages:Version" value="3.0.0.0" />
    <add key="webpages:Enabled" value="false" />
    <add key="ClientValidationEnabled" value="true" />
    <add key="UnobtrusiveJavaScriptEnabled" value="true" />
    <add key="ida:ClientId" value="" />
    <add key="ida:AADInstance" value="https://login.microsoftonline.com/" />
    <add key="ida:Domain" value="" />
    <add key="ida:TenantId" value="" />
    <add key="ida:PostLogoutRedirectUri" value="https://localhost:44341/signin-oidc" />
</appSettings>

Also, AccountControlller is not being called:

namespace OidcTestDemo.Controllers
{
    public class AccountController : Controller
    {
        public void SignIn()
        {
            if (!Request.IsAuthenticated)
            {
                HttpContext.GetOwinContext().Authentication.Challenge(new AuthenticationProperties { RedirectUri = "/" },
                    OpenIdConnectAuthenticationDefaults.AuthenticationType);
            }
        }

        public void SignOut()
        {
            string callbackUrl = Url.Action("SignOutCallback", "Account", routeValues: null, protocol: Request.Url.Scheme);

            HttpContext.GetOwinContext().Authentication.SignOut(
               new AuthenticationProperties { RedirectUri = callbackUrl },
               OpenIdConnectAuthenticationDefaults.AuthenticationType, CookieAuthenticationDefaults.AuthenticationType);
        }

        public ActionResult SignOutCallback()
        {
            if (Request.IsAuthenticated)
            {
                // Redirect to home page if the user is authenticated.
                return RedirectToAction("Index", "Home");
            }

            return View();
        }
    }
}

Answers

It seems like you're encountering an issue with the authentication flow in your ASP.NET MVC application using Azure Active Directory (AAD). Here are a few things to check:

  1. Client ID and Tenant ID: Ensure that the values for ida:ClientId and ida:TenantId in your Web.config file are correctly set to the client ID and tenant ID of your Azure AD application.

  2. Authority URL: Double-check the authority variable in your Startup.Auth.cs file. It should be constructed as https://login.microsoftonline.com/<tenant_id>/v2.0.

  3. Redirect URIs: Verify that the redirect URIs configured in your Azure AD application match the ones used in your application. Ensure that they include both signin-oidc and signout-callback-oidc endpoints.

  4. AccountController: Ensure that your AccountController is properly set up and accessible. Check that it's being invoked correctly and that the SignIn action is being called when authentication is required.

  5. Logging: Add logging statements to your authentication middleware setup (ConfigureAuth method in Startup.Auth.cs) to check if it's being executed and if any errors are being thrown during the authentication process.

  6. Authentication Flow: Ensure that the flow of your application correctly initiates the authentication process when accessing protected routes. Make sure that the SignIn action of your AccountController is triggered when authentication is required.

By reviewing these points and troubleshooting any discrepancies, you should be able to identify and resolve the issue with the authentication redirection in your ASP.NET MVC application.

#.net