StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POWindowsIdentity.Impersonate and PostBack issue
text
Body
copied!<p>I am writing an ASP website that uses Forms security and Active Directory.</p> <p>I allow the user to login using the Windows API:</p> <pre><code>[DllImport("advapi32.dll", SetLastError = true)] public static extern bool LogonUser(string pszUsername, string pszDomain, string pszPassword, int dwLogonType, int dwLogonProvider, ref IntPtr phToken); </code></pre> <p>This gives me a Login Token Pointer which I than save in a session variable:</p> <pre><code>bool returnValue = LogonUser(txtUserName.Text, domainName, txtPassword.Text, LOGON32_LOGON_INTERACTIVE, LOGON32_PROVIDER_DEFAULT, ref TokenHandle); if (!returnValue) { lblErrorMessage.Text = "Incorrect Username or Password"; lblErrorMessage.Visible = true; return; } Session["TokenHandle"] = TokenHandle; </code></pre> <p>Now when I get redirected back to my Default.aspx page I want to Impersonate the user that has logged in. This way I don't have to hard code a SQL connection string user name, I can just use integrated security. I do this on <strong>Page Load</strong> as follows:</p> <pre><code>if (Session["TokenHandle"] != null) { IntPtr tokenHandle = new IntPtr(0); tokenHandle = (IntPtr)Session["TokenHandle"]; WindowsIdentity.Impersonate(tokenHandle); } </code></pre> <p><strong>Here is the problem:</strong></p> <p>It all works great the first time I hit Default.aspx however as soon as I do a postback it looses the impersonation and I get an error:</p> <p><em>Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.</em> </p> <p>Now I know this code should work, I have used it in other project. I am just missing something here.</p> <p>Also I am using DevExpress.Web.ASPxGridView.v9.2 component, I am not sure if it has anything to do with it.</p> <p>Please help.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload