I have read the various posts and information about the most awesome UltiDev Web Server Pro (actually using it). Am I under the wrong assumption with regards to acquiring the identity of a user accessing my intRAnet application where I thought with v14 (now v15) that I would be able to acquire such with any of the following?

string userID = HttpContext.Current.User.Identity.Name;
string userID = ((WindowsIdentity)User.Identity).Name;
string userID = Request.ServerVariables["LOGON_USER"];

I would like to be able to get the network user ID (or whatever you would prefer to call it) to not only automatically authenticate and allow access; but, to load user information to use in the web application such as user name, security level, manager, etc.

Is there a trick that I am missing?

I have <authentication mode="Windows"/> set in the web.config file and I have tried various things to no avail.

Your help would be greatly appreciated!

BTW: My application does acquire my own userID ONLY when launching/debugging via Visual Studio (2008).

Thanks.

I recently upgraded to UWS along with going to Visual Studio 2010 and the windows authentication did not catch again using HttpContext.Current.User.Identity.Name for some unknown reason (authentication in web.config is set to windows). I don't remember seeing your response back then; but, I changed the code to use this.Request.LogonUserIdentity.Name and I was back in business.

So thank you for your response (8 months belated) and keep up the great work on UWS!!!

If this needs to be in a different thread, please move it. Thanks.

There is a new authentication issue that I am unable to resolve with regards to authentication from ASP.NET on UWS Pro to SQL Server (Windows Authentication). On the machine hosting UWS with Visual Studio 2010, my ASP.NET application (.NET 4.0, C#) works both inside and outside of Visual Studio. However, when connecting to the applicaiton from a remote machine (same domain), I get an error from SQL Server: Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.

NOTE: The app pool in UWS is set to Windows (Integrated) only and the app is set to Windows (authentication) with Impersonation (true).

Is there something different with UWS than IIS that is causing UWS to recognize the actual Windows account; but, not being able to pass it through to SQL Server if not on the same machine as UWS and the app? I really need to figure this out as I need to port local databases to other servers where our company requires Windows Authentication to access SQL Server and I do not have access to IIS (at this time).

Thanks!

---

From the same computer as UWS and app: No problems!

From a computer other than the preceding, but on the same network: ResourceUtilization.LogIn.Page_LoadComplete[LoadUserData](): ResourceUtilization.UserInfo.LoadUserData(MYUSERID): Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.

Thank you for the very quick response!!!! :-)

As to the clarifications...

This only happens when I try to run the web (intranet) app when on a client computer rather than the UWS server. On the server, no problems with the app or SQL Server. On the client, a problem with SQL Server but no problem with the app.

Also, I log in with an Active Diretory (AD) domain user account and both the server and client are members of said domain.

UWS and application are on machine A
SQL Server is on machine B
Client is machine C

When the application is run from machine A, both the application and SQL Server have no problem with authentication
When the application is run from machine C, SQL Server has a problem with the authentication where the application has no problem

Of course, the application fails when run from machine C because SQL Server is the back end (not for the session, but for the data that is used in the application).

Hope this is clearer for you.

Thanks.

Thank you very much!

It sure does seem to be a "double-hop" issue; but, I am not sure how to resolve the issue with regards to UWS and any security settings (per the link in the double-hop article, http://blogs.technet.com...is-and-sql-server.aspx, or otherwise).

I know that other teams in the company using IIS for intranet applications over SQL Server do not have the "double-hop" issue; but, none are able to tell me what settings (and where) help them to achieve success....and, of course, they are using pure IIS as opposed to your awesome UWS product.

BTW: I only have admin to the machine that runs UWS and the applications; so I am unable to change anything on the SQL Server machine or in AD.

Thanks.

I will install IIS and test it as soon as feasible without causing any issues to the users/testers of the various running applications. Once I do get it installed and give it a test, I will post my results.

BTW: I did pose the resolution of making sure the machine has the Kerberos Delegation set up for access to SQL Server with the relevant parties and hopefully it will be simple enough to confirm (and make happen).

Thanks!