A better way to get a Windows Username using Forms

问题:

I've inherited a project that uses forms authentication, but a recent feature request requires me to get the Windows username of some users.

It's a website that uses Forms authentication (and I do NOT want to change this, it would be too much work at this point) but I have had a feature request to allow our internal users to login more easily (usually without having to put in their password or username).

My current method is HORRIBLE, it involves checking the ip address to see if they're connecting from one of our IPs, if they are, redirecting them to a separate project that uses Windows Authentication which then redirects them back to the original page with a query string containing their username (if I am forced to remain with this method I'll probably need to encrypt this although it's still not as secure as I would like).

I can perform the windows authentication relatively easily inside my app, however the hard part is getting the windows username. I could not figure out how to do it, hence my pretty ugly method.

Any help would be GREATLY appreciated.

EDIT: My secondary app just does this:

string username = HttpContext.Current.User.Identity.Name;
string retpath = Request.QueryString["retpath"];
Response.Redirect("http://" + retpath + "?id=" + username);

回答1:

This article contained the answer, (thanks vinodpthmn): http://msdn.microsoft.com/en-us/library/ms972958.aspx I'd found links to this article in my research, but none of them worked! Glad I was finally able to read it and solve my problem.

As I mentioned I only needed to get the windows username of clients, but that turned out to be quite troublesome, thankfully the actual solution was relatively simple.

Firstly, you need to create an additional login page (I called mine winlogin.aspx) and set that as the default login page in your Web.Config file, like this:

<authentication mode="Forms">
      <forms name="something" defaultUrl="default.aspx" loginUrl="winlogin.aspx" protection="All" slidingExpiration="true" timeout="90"/>
    </authentication>

Inside the winlogin.aspx.cs file is where you authenticate windows users and use

FormsAuthentication.RedirectFromLoginPage(username, false/true);

To redirect them to wherever they were going. The actual winlogin.aspx page should be blank, users will never see it.

You need to publish to your testing web server for this next part: You access the file properties of winlogin.aspx in IIS manager and set WindowsAuthentication to true and Anonymous Authentication to false. You also need to create a custom 401 error page pointer (mine points to my old Login.aspx page).

Users that can login with windows authentication will do so, everybody else will be redirected to the old login page.

Voila!

There are a couple of issues however, you lose your return URL (you can't use "=" in the link to a custom 401 error page, so nothing can be parsed) so you'll probably want to set a cookie whenever people are redirected to the winlogin page and access that cookie in your forms login page to redirect the user appropriately.

If anybody has any questions, I suggest reading the article linked above, or feel free to ask questions here.

Thanks everybody for your help!

回答2:

You could use directory services

PrincipalContext pc = null;
UserPrincipal principal = null;
var username = User.Identity.Name;
pc = new PrincipalContext(ContextType.Domain, "give your domain name here");
principal = UserPrincipal.FindByIdentity(pc, userName);
var firstName = principal.GivenName ?? string.Empty;
var lastName = principal.Surname ?? string.Empty;

please add reference for System.DirectoryServices.AccountManagement