V
Vadim P
I am authenticating against an AD using DirectoryEntry and binding by getting
NativeObject. Just two lines, create DirectoryEntry and call NativeObject.
Functionally everything works. However, it takes over 13 sec to return
NativeObject when invoked ASP.Net page. The same exact code in a test exe
returns in less that one second. The LDAP are inside a utility class that
lives in library, so the only difference is the how they are being called.
I traced through the web page and the business object down to the statement
level and confirmed that it is in fact entry.NativeObject consumes all of
that time. I added ASPNET and IUSR_xxxxx accounts to the Administrators
group. I tried every reasonable AuthenticationTypes value.
If the user authenticates, logs out and authenticates again, the login is
very quick. I assume this is due to caching.
Any ideas on how I can improve performance? What should I try next?
Thank you,
-Vadim
NativeObject. Just two lines, create DirectoryEntry and call NativeObject.
Functionally everything works. However, it takes over 13 sec to return
NativeObject when invoked ASP.Net page. The same exact code in a test exe
returns in less that one second. The LDAP are inside a utility class that
lives in library, so the only difference is the how they are being called.
I traced through the web page and the business object down to the statement
level and confirmed that it is in fact entry.NativeObject consumes all of
that time. I added ASPNET and IUSR_xxxxx accounts to the Administrators
group. I tried every reasonable AuthenticationTypes value.
If the user authenticates, logs out and authenticates again, the login is
very quick. I assume this is due to caching.
Any ideas on how I can improve performance? What should I try next?
Thank you,
-Vadim