My web.config contains:
<authorizatio n>
<deny users="?" />
</authorization>
<authenticati on mode="Windows" />
<identity impersonate="tr ue" userName="" password="" />
My connection string in page.aspx.vb contains:
oSQLConn.Connec tionString = "Data Source=" & Server & "," & PortNo &
";Initial Catalog=master; Integrated Security=SSPI;"
When the connection is opened:
oSQLConn.Open()
No matter what I do it always passes anonymous user instead of logged on
user and fails to open the connection. Only if I edit web.config and supply
userName & password
<identity impersonate="tr ue" userName="mynam e" password="mypas sword" />
then the connection is opened with supplied credentials.
Is this a bug? Is there a workaround? Am I missing something?
I'm sure bunch of ppl had to run into this problem. How did you fix it?
Machuga
<authorizatio n>
<deny users="?" />
</authorization>
<authenticati on mode="Windows" />
<identity impersonate="tr ue" userName="" password="" />
My connection string in page.aspx.vb contains:
oSQLConn.Connec tionString = "Data Source=" & Server & "," & PortNo &
";Initial Catalog=master; Integrated Security=SSPI;"
When the connection is opened:
oSQLConn.Open()
No matter what I do it always passes anonymous user instead of logged on
user and fails to open the connection. Only if I edit web.config and supply
userName & password
<identity impersonate="tr ue" userName="mynam e" password="mypas sword" />
then the connection is opened with supplied credentials.
Is this a bug? Is there a workaround? Am I missing something?
I'm sure bunch of ppl had to run into this problem. How did you fix it?
Machuga
Comment