Impersonate using Forms Authentication

后端 未结 5 988
说谎
说谎 2020-11-29 02:15

I have an ASP.NET site that must use Forms Authentication and not Windows Authentication to access a ActiveDirectoryMembershipProvider. The site must use forms

5条回答
  •  臣服心动
    2020-11-29 03:07

    Impersonating a user using Forms Authentication can be done. The following code does work.

    The Visual Studio Magazine article referred to by Robert is an excellent resource. There are a some issues with the example code in the article, so I've included some working code below.

    Note: If you are using Visual Studio, make sure to launch it "Run as Administrator" to avoid problems with UAC blocking impersonation.

    // in your login page (hook up to OnAuthenticate event)
    protected void LoginControl_Authenticate(object sender, AuthenticateEventArgs e)
    {
        int token;
        // replace "YOURDOMAIN" with your actual domain name
        e.Authenticated = LogonUser(LoginUser.UserName,"YOURDOMAIN",LoginUser.Password,8,0,out token);
        if (e.Authenticated) {
            Session.Add("principal", new WindowsPrincipal(new WindowsIdentity(new IntPtr(token))));
        }
    }
    
    [DllImport("advapi32.dll", SetLastError = true)]
    public static extern bool LogonUser(string lpszUsername, string lpszDomain, string lpszPassword,
        int dwLogonType, int dwLogonProvider, out int TokenHandle);
    
    
    // in global.asax.cs
    void Application_PreRequestHandlerExecute(object send, EventArgs e)
    {
        if (Thread.CurrentPrincipal.Identity.IsAuthenticated == true && HttpContext.Current.Session != null) {
            WindowsPrincipal windowsPrincipal = (WindowsPrincipal)Session["principal"];
            Session["principal"] = (GenericPrincipal)Thread.CurrentPrincipal;
            Thread.CurrentPrincipal = windowsPrincipal;
            HttpContext.Current.User = windowsPrincipal;
            HttpContext.Current.Items["identity"] = ((WindowsIdentity)windowsPrincipal.Identity).Impersonate();
        }
    }
    
    // in global.asax.cs
    void Application_PostRequestHandlerExecute(object send, EventArgs e)
    {
        if (HttpContext.Current.Session != null && Session["principal"] as GenericPrincipal != null) {
            GenericPrincipal genericPrincipal = (GenericPrincipal)Session["principal"];
            Session["principal"] = (WindowsPrincipal)Thread.CurrentPrincipal;
            Thread.CurrentPrincipal = genericPrincipal;
            HttpContext.Current.User = genericPrincipal;
            ((WindowsImpersonationContext)HttpContext.Current.Items["identity"]).Undo();
        }
    }
    
    // test that impersonation is working (add this and an Asp:Label to a test page)
    protected void Page_Load(object sender, EventArgs e)
    {
        try {
            // replace YOURSERVER and YOURDB with your actual server and database names
            string connstring = "data source=YOURSERVER;initial catalog=YOURDB;integrated security=True";
            using (SqlConnection conn = new SqlConnection(connstring)) {
                conn.Open();
                SqlCommand cmd = new SqlCommand("SELECT SUSER_NAME()", conn);
                using (SqlDataReader rdr = cmd.ExecuteReader()) {
                    rdr.Read();
                    Label1.Text = "SUSER_NAME() = " + rdr.GetString(0);
                }
            }
        }
        catch {
        }
    }
    

    Update:

    You should also handle Application_EndRequest, because calls like Response.End() will bypass Application_PostRequestHandlerExecute.

    Another issue is that the WindowsIdentity may get garbage collected, so you should create a new WindowsIdentity and WindowsPrincipal from the logon token on every request.

    Update2:

    I'm not sure why this is getting downvoted, because it works. I've added the pinvoke signature and some test code. Again, launch Visual Studio using "Run as Administrator". Google how to do that if you don't know how.

提交回复
热议问题