2015 Update: There are now some modules that implement Windows-integrated authentication. node-sspi uses SSPI (the Windows security API) to handle the server side of things, but does not do client auth. There are several client implementations such as http-ntlm, but they are not truly integrated since they require the user password — they do not … Read more
If you are using Windows Authentication, you need to use NTLM: curl –ntlm –user username:password http://example.com
To get the UserName of the authenticated user: HttpContext.Current.User.Identity.Name;
These are the different variables you have access to and their values, depending on the IIS configuration. Scenario 1: Anonymous Authentication in IIS with impersonation off. HttpContext.Current.Request.LogonUserIdentity.Name SERVER1\IUSR_SERVER1 HttpContext.Current.Request.IsAuthenticated False HttpContext.Current.User.Identity.Name – System.Environment.UserName ASPNET Security.Principal.WindowsIdentity.GetCurrent().Name SERVER1\ASPNET Scenario 2: Windows Authentication in IIS, impersonation off. HttpContext.Current.Request.LogonUserIdentity.Name MYDOMAIN\USER1 HttpContext.Current.Request.IsAuthenticated True HttpContext.Current.User.Identity.Name MYDOMAIN\USER1 System.Environment.UserName ASPNET Security.Principal.WindowsIdentity.GetCurrent().Name SERVER1\ASPNET Scenario … Read more
For dev I am using IISExpress with development server properties of the MVC project set up so that Anonymous Authentication is Disabled and Windows Authentication is Enabled. The web config is deployed using our TFS build server to test and release servers for which authentication is also setup as above and works in those locations … Read more
I think nowadays you can just set the withCredentials property of the request object to true, e.g.: $.ajax({ type: “GET”, url: service_url, dataType: “xml”, data: “ParamId=” + FormId.value, processData: false, xhrFields: { withCredentials: true }, error: function(XMLHttpRequest, textStatus, errorThrown) { ajaxError(XMLHttpRequest, textStatus, errorThrown); }, success: function(xml) { DoSomething(xml); } }); That causes existing authentication headers/cookies … Read more
The “pre Windows 2000” name i.e. DOMAIN\SomeBody, the Somebody portion is known as sAMAccountName. So try: using(DirectoryEntry de = new DirectoryEntry(“LDAP://MyDomainController”)) { using(DirectorySearcher adSearch = new DirectorySearcher(de)) { adSearch.Filter = “(sAMAccountName=someuser)”; SearchResult adSearchResult = adSearch.FindOne(); } } someuser@somedomain.com.au is the UserPrincipalName, but it isn’t a required field.
Probably the best and the cleanest code that I have seen so far is this: var credentials = new UserCredentials(domain, username, password); Impersonation.RunAsUser(credentials, logonType, () => { // do whatever you want as this user. }); Just follow Github or Nuget.
I have investigated the source code of HttpClientHandler (the latest version I was able to get my hands on) and this is what can be found in SendAsync method: // BeginGetResponse/BeginGetRequestStream have a lot of setup work to do before becoming async // (proxy, dns, connection pooling, etc). Run these on a separate thread. // … Read more
The issue here is that modern versions of Windows (Windows XP SP2, Windows Server 2003 SP1 and up) include a loopback check security feature that is designed to help prevent reflection attacks on your computer. Therefore, authentication fails if the FQDN or the custom host header that you use does not match the local computer … Read more