views:

45

answers:

1

I have a setup where I impersonate an AD user as described here. The app connects to the (Oracle) database using integrated security, but the impersonated credentials are not propagated to the database.

Are there any known issues with impersonating AD users and accessing the database with integrated security?

+1  A: 

I've seen this in Windows Web Applications where AD impersonation would not work because SQL Server would not trust the relaying party, i.e. IIS. In my example, basically IIS was telling SQL Server that the credentials provided are legitimate, but SQL Server would not trust the web server to present these credentials, some times called the double hop issue. Have you tried in AD to trust your application/web server for delegation?

RandomNoob
This could be it, but I will have to talk to our sysadmins to see if the fix works. I'll try it out and get back.
martinnjensen
Trusted for Delegation is what's needed to pass the Kerberos identity off to the next "hop".
ParanoidMike