windows-authentication

I am trying to use IIS 7.5 Application Pool identity as login on SQL Server 2008 R2 so that my ASP.NET web app can connect to the database... Using this approach worked fine on my local dev machine (IIS 7.5 and SQL Server 2008 R2 on same machine). However, when I try to set up the same on production (IIS and SQL servers are separate) I am unable to add "IIS APPPOOL\MyAppAppPool" login to SQL Server 2008 R2. Notice that in either case you cannot use "Browse..." when creating a login in SQL Server since "IIS APPPOOL\MyAppAppPool" user identity is dynamic (or "special")... Any ideas? Update: For

Let me give some background before I ask my question. I’m at a shop that primarily runs Windows. We have several batch applications running on Windows Servers (mostly 2003). Most of these batch applications are written in C# and C++; however we have a handful of applications that are written in Java. The batch Java applications are connecting to a SQL Server 2005 database using JDBC. Please note we are not using an application server. Currently we store database connection information (database, username, & password) in the Windows Registry. Unfortunately these really unfriendly auditors (bad

I want to use the ASP.NET MVC 5 for my web app. I need use the windows authentication . If I use the windows authentication where is the best place for reading user information (userid and roles) and store its to the Session ? I have the method for getting the user information by username from the database like this: public class CurrentUser { public int UserId { get; set; } public string UserName { get; set; } public Roles Roles { get; set; } } public enum Roles { Administrator, Editor, Reader } public class AuthService { public CurrentUser GetUserInfo(string userName) { var currentUser = new

I have my asp.net web server setup to use windows authentication. It is authenticating just fine with my current logged in user. I can verify this by viewing ... HttpContext.Current.User.Identity.Name And I can verify that I am authenticated by viewing... HttpContext.Current.User.Identity.IsAuthenticated However, when I call the .IsInRole function I get the trust relationship error... HttpContext.Current.User.IsInRole("accounting") I have found online references to problems with supplying domain name with the role name (domain\accounting), but I still get the same error. Any suggestions on

I am trying to create a custom HttpModule which controls which users can view a site. I am trying to leverage Windows Authentication to do this. On an individual page, I would probably do something like this: if (HttpContext.Current.User.Identity.Name.Contains("jsmith")) { Response.Write("You do not have the correct permissions to view this site."); Response.End(); } But because I want to make this more configurable at the application level, I would like to use an HttpModule. Here is the start that I have made on the code: using System; using System.Web; public class CustomAuthHttpModule :

I would like to be able to detect, from ASP.NET code, whether IIS currently has "Windows Authentication" "available"? Starting from my application installed and currently running under "Anonymous Access", I want to detect: "Windows Authentication" component has actually been installed in IIS (e.g. some IIS7 have it not installed by default); and... "Windows Authentication" is actually "Enabled" on my virtual root/location. I want this information to let the Administrator know whether he needs to take action in IIS before he actually attempts to switch it on on my application. (Hence, for

Quick... How to use Windows Authentication to SQL Server with the Mono SQL Client running on Windows without a username+ password in the connection string? More... We have to use Mono to support multiple platforms for some components of our app This is an external limitation that we can't change We will run the components that access the database only on Windows The portability/OS-agnostic features of the Mono SQL Client add no value That is, any component running on non-Windows will not access the SQL Server database The process runs under some Windows user (real user, service account,