Re: integrated security and using NT credentials vs. ASP.NET
From: Val Mazur (group51a_at_hotmail.com)
Date: 05/11/04
- Next message: Cindy Winegarden: "Re: OLEDB and FoxPro Tables"
- Previous message: Vineet Batta: "Cross -Site Scripting and SQL Data Reader"
- In reply to: beaverduck: "integrated security and using NT credentials vs. ASP.NET"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 10 May 2004 20:57:22 -0400
Hi,
What you need to do is to assign permissions for the ASPNET account from the
SQL Server. Check next KB about this
http://support.microsoft.com/default.aspx?scid=kb;en-us;316989&Product=aspnet
-- Val Mazur Microsoft MVP "beaverduck" <kmiller@everestinc-dot-com.no-spam.invalid> wrote in message news:40a0098a$1_2@127.0.0.1... > My connection string is set to use integrated security. When I try to > log into my data source via my asp.net application, I get the > following error: > > "Login failed for user '(null)'. Reason: Not associated with a trusted > SQL Server connection" > > My NT login name is setup in the data source as a user and it has been > granted the necessary rights against the database objects. > > I thinking that the default user name for asp.net application is the > asp.net machine account, and because the database does not have this > user established, I'm getting this permission error. > > Does anyone know the best way to avoid this and have the credentials > of the logged in user be used via the integrated security connection > string? >
- Next message: Cindy Winegarden: "Re: OLEDB and FoxPro Tables"
- Previous message: Vineet Batta: "Cross -Site Scripting and SQL Data Reader"
- In reply to: beaverduck: "integrated security and using NT credentials vs. ASP.NET"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|