DirectoryEntry Impersonate or WindowsIdentity Impersonate?
From: Bill Belliveau (anonymous_at_discussions.microsoft.com)
Date: 01/28/04
- Next message: Ken Schaefer: "Re: Network Credentials not passing in Authentication mode"
- Previous message: Shriop: "Re: Network Credentials not passing in Authentication mode"
- Next in thread: Joe Kaplan \(MVP - ADSI\): "Re: DirectoryEntry Impersonate or WindowsIdentity Impersonate?"
- Reply: Joe Kaplan \(MVP - ADSI\): "Re: DirectoryEntry Impersonate or WindowsIdentity Impersonate?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Tue, 27 Jan 2004 16:21:06 -0800
Another security question.
Our project interfaces with the Active Directory. To satisfy the security issues, we have a couple options when we talk to the Directory.
1. Use the WindowsIdentity to impersonate the current user either by impersonating the User.Identity where available or by using UserLogon.
2. Making a DirectoryEntry for each query/edit and send the username and password per request as part of the DE.
My questions are what are the security and performance impact of these methods?
Thanks,
Bill
- Next message: Ken Schaefer: "Re: Network Credentials not passing in Authentication mode"
- Previous message: Shriop: "Re: Network Credentials not passing in Authentication mode"
- Next in thread: Joe Kaplan \(MVP - ADSI\): "Re: DirectoryEntry Impersonate or WindowsIdentity Impersonate?"
- Reply: Joe Kaplan \(MVP - ADSI\): "Re: DirectoryEntry Impersonate or WindowsIdentity Impersonate?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|