A
Andreas
Hello all,
I have some difficulties understanding my problem here, so I am not to sure
if this is the right group to post.
I use Studio 2k5 on a XP machine asp.net 2. The application is working fine
running on the studio development server. So the user login / authentication
/ db access, all good. (Using SQL server express 2k5)
if I take the application to the server, either an xp/iis5 or 2k3 iis6
machine ... the application is working fine, including dynamic parts loaded
from a second, my own SQL DB. But user login always fails ...no error msg,
just ...'Your login attempt was not successful'.
I discovered, if I use
<identity impersonate="true" userName="Administrator"
password="Password" />
on the (live)server, given a full admin credential, it all works fine.
The thing I don't understand is, I use the default aspnetdb.mdf database
studio creates for you to handle the user authentication / Roles. What am I
missing here ? Why is it working on the dev server, but not on IIS.
I don't see why, and am a little concerned about, give'n admin credentials
to the application just so authentication can take place. I know I can hash
the login/pass and even place it in the registry, so it's not placed inside
the web.config, but this doesn't sound right.
As far as I understand it, the ASPNET user account is used from the
application to handle any file requests, and therefore also to connect to
the DB and is setup automatically, at least on th XP server box.
From all I can tell, the authentication is denied because the application
has no authorization to access the DB, but I don't understand why.
Do I have to change something in the DB ? Add ASPNET account as user of the
DB maybe?
I have some difficulties understanding my problem here, so I am not to sure
if this is the right group to post.
I use Studio 2k5 on a XP machine asp.net 2. The application is working fine
running on the studio development server. So the user login / authentication
/ db access, all good. (Using SQL server express 2k5)
if I take the application to the server, either an xp/iis5 or 2k3 iis6
machine ... the application is working fine, including dynamic parts loaded
from a second, my own SQL DB. But user login always fails ...no error msg,
just ...'Your login attempt was not successful'.
I discovered, if I use
<identity impersonate="true" userName="Administrator"
password="Password" />
on the (live)server, given a full admin credential, it all works fine.
The thing I don't understand is, I use the default aspnetdb.mdf database
studio creates for you to handle the user authentication / Roles. What am I
missing here ? Why is it working on the dev server, but not on IIS.
I don't see why, and am a little concerned about, give'n admin credentials
to the application just so authentication can take place. I know I can hash
the login/pass and even place it in the registry, so it's not placed inside
the web.config, but this doesn't sound right.
As far as I understand it, the ASPNET user account is used from the
application to handle any file requests, and therefore also to connect to
the DB and is setup automatically, at least on th XP server box.
From all I can tell, the authentication is denied because the application
has no authorization to access the DB, but I don't understand why.
Do I have to change something in the DB ? Add ASPNET account as user of the
DB maybe?