Moik
January 17th, 2008, 12:22 PM
I've written an ASP.Net application to synchronise an Active Directory with an LDAP. In the development environment this works fine, but once deployed to the live website it seems to keep running over and over.
There are two ways to trigger the sync. One is via a web page with a button which must be mouse clicked by hand, the other is via a SOAP call when a change is made to the LDAP. The SOAP call is currently disabled as the code that makes the call is currently commented out and no-one is messing with the LDAP during testing anyway.
I have isolated the problem to IIS as the application uses a web.config file that tells it which branches of the LDAP to synchronise. By setting it to an imaginary branch it stops the constant sync. As soon as you put a real branch back into the conf file it is synching over and over, and this in turn is preventing the AD entries being used by Citrix.
The only difference I can see between the development IIS and the live one is that the live IIS is hosting more than one website. Is there a possibility that another website is triggering the synch event, even though LDAP to AD has its own application pool?
There are two ways to trigger the sync. One is via a web page with a button which must be mouse clicked by hand, the other is via a SOAP call when a change is made to the LDAP. The SOAP call is currently disabled as the code that makes the call is currently commented out and no-one is messing with the LDAP during testing anyway.
I have isolated the problem to IIS as the application uses a web.config file that tells it which branches of the LDAP to synchronise. By setting it to an imaginary branch it stops the constant sync. As soon as you put a real branch back into the conf file it is synching over and over, and this in turn is preventing the AD entries being used by Citrix.
The only difference I can see between the development IIS and the live one is that the live IIS is hosting more than one website. Is there a possibility that another website is triggering the synch event, even though LDAP to AD has its own application pool?