login

Hot Topic

Object reference not set to an instance of an object.
Compiled HTML helpfile does not work when application is installed
Insert Command Problems
Email Method does not send from port 25???
SelectSingleNode
how to not include base class in shema
ArrayList Serialization Error
How to run an sql stored procedure on my aspx page ?
MSXML Problems
impersonating ASP.NET

.NET Development

reading file size, date, name from the internet
socket class raise event
How to find the last occurence of <p> within a textblock tiltled <h2>??
Synchronize AS400 with Access???
Active Directory: Enumerate all groups that a user belogs to, including nested groups.
.NET 3.0 Failing to install on XP
System.Net.WebException
NullReferenceException vs. invalid address
System.Speech.Recognition GrammarBuilder.AppendWildcard
InfoTip Help!

login

I have created a .net 2.0 windows application.
Trusted connection to connect to sql server.
Using sql server System_User, the application gets the loginname for the user in sql server.

Now I have created webservices to be used in this project.
It seems that I can not use my existng method (Trusted connection) to get the loginName of the user.
So in sql server, created a webuser account.
Everyone now is using the system using the webuser account.
But, this way I do not know exactly which user is using the application because all I see is webuser hitting the database through the application.
How do you suggest I log the users
I was thinking may be I should create roles on the network. i.e. NormalUsers, managers, chairmen, etc,...
Then add the appropriate users to these roles on the network.
I can then create a login screen.
Windows application can then find the user identity. This user can then be traced from the users table in sql server and get it's ID. ID can be used to be inserted into the Audit table.
What do you think please
THnaks

Answer this question

login

  • Kamii47

    You can use impersonation but that won't solve your issue if I understand correctly. You get a major advantage by just having one user, namely that you don't have to manage the logins and you can make changes easily. The main problem I see with the way you're proposing to do it, is HTTP is stateless, how will you know when someone isn't using it any longer with that scheme Is that an issue

  • MagedSalah

    You have to specify the Security of your web app from IIS.

    Set the Security to Integrated in your IIS



  • login
Answer this question