S
Shikari Shambu
Hi,
I have an ASP.NET intranet site that is using a central directory (ADAM)
that the users authenticate against.
We chose to use a separate ADAM instead of leveraging the corporate AD.
To get the user authenticated against our ADAM I have to set up the site to
use Windows Authentication and set <identitty impersoante="true/> in
web.config.
However, when I do that all calls to the underlying systems (like DB) are
made under the user context. Is there a way to make sure that calls to the
database etc... continue to use a application specific NT account.
How would you setup the authentication/ impersonation scheme for a scenario
like this.
TIA
I have an ASP.NET intranet site that is using a central directory (ADAM)
that the users authenticate against.
We chose to use a separate ADAM instead of leveraging the corporate AD.
To get the user authenticated against our ADAM I have to set up the site to
use Windows Authentication and set <identitty impersoante="true/> in
web.config.
However, when I do that all calls to the underlying systems (like DB) are
made under the user context. Is there a way to make sure that calls to the
database etc... continue to use a application specific NT account.
How would you setup the authentication/ impersonation scheme for a scenario
like this.
TIA