Security Issues between SQL 2000 and ASP NET. Need help badly.

  • Thread starter Thread starter IcedCrow
  • Start date Start date
I

IcedCrow

I have stumbled upon a serious problem and I hope someone
can help me out.

I have programmed a web service in VB.NET.

When I use integrated security for the piece, of course
it does not use my log in but the ASP log in. No
problem. I get an error.

So first in experiment I try and use the sa account. I
type his account in and password and then I get a "User
not Trusted" error even though the credentials I passed
were correct.

So then I add the ASPNET user to SQL and give him public
access to a database. I try passing the ASPNET login
with the password and I get a time out error.

I then try using plain old integrated security but it
again times out.

Does anyone know what I need to do to set this
connection?? (I am also using ADO.NET)

Thanks!
 
Hi Iced Crow,
Did you know that the public.asp.net newsgroup exist.
I believe that in that newsgroup you will get a faster answer to this kind
of questions than in the vb.net language group.
Cor
 
IcedCrow said:
I have programmed a web service in VB.NET.

When I use integrated security for the piece, of course
it does not use my log in but the ASP log in. No
problem. I get an error.

So first in experiment I try and use the sa account. I
type his account in and password and then I get a "User
not Trusted" error even though the credentials I passed
were correct.

So then I add the ASPNET user to SQL and give him public
access to a database. I try passing the ASPNET login
with the password and I get a time out error.

I then try using plain old integrated security but it
again times out.

Does anyone know what I need to do to set this
connection?? (I am also using ADO.NET)
Click to expand...

You may want to turn to the ng for ASP.NET related questions:

<
Web interface:

<http://msdn.microsoft.com/newsgroup...roup=microsoft.public.dotnet.framework.aspnet>
 
Using the Windows Only security setting in SQL with an ASP.net or ASP.net
Web service is a pain. The best option you have is to change your security
setting in SQL to use SQL Server and Windows. Then you can create a SQL
login and use that in your application. This setting is almost for sure the
reason you are not able to use sa for a login (not that you would use sa for
a program to login anyway *g*)

Kirk Graves
 
Kirk,

Thank you very much for the reply. I was up late last night pounding on
this thing and this morning I was finally able to solve my puzzle doing
exactly what you said. Once I set it to SQL security everything was
happy.

I realize I wouldn't use SA in a production enviornment, this is for a
classroom enviornment.

I have experience with DBAs not even wanting to grant anything to the
ASP or ASPNET user accounts... I'm sure there will be much flack given
on this but... sa it is for now.

Again thanks for the reply.

~IC
 
Back
Top